IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Bug: Access ODBC Connection file extension requirement
Tomi_Maila
post 15. May 2008, 07:18
Post #1


new Member
*

Group: Members
Posts: 4
Joined: 15.05.2008
Member No.: 57
LV Version: 8.5.1
Zertifizierung: CLAD
LV User seit: 2004



Hallo Christian,

Your ADO Toolkit requires the Access Database file extension to be .mdb. However Access doesn't require the databases to be of this extension. Old versions of Access databases were based on Jet database engine. I've some application that uses Jet DB engine and multiple databases with various file extensions. The databases can be opened with your ADO Toolkit if I remove the file extension requirement from your code. Can you please consider removing the requirement for certain file extension so I can use unmodified version of ADO Toolkit in my code...


Tomi
Go to the top of the page
 
+Quote Post
CB
post 15. May 2008, 12:41
Post #2


proven Member
****

Group: Administrators
Posts: 315
Joined: 16.10.2006
From: Düsseldorf
Member No.: 2
LV Version: current
Zertifizierung: CLA
LV User seit: 2001



QUOTE(Tomi_Maila @ 15. May 2008, 08:18) *
Hallo Christian,

Your ADO Toolkit requires the Access Database file extension to be .mdb. However Access doesn't require the databases to be of this extension. Old versions of Access databases were based on Jet database engine. I've some application that uses Jet DB engine and multiple databases with various file extensions. The databases can be opened with your ADO Toolkit if I remove the file extension requirement from your code. Can you please consider removing the requirement for certain file extension so I can use unmodified version of ADO Toolkit in my code...
Tomi


for sure.

If you can tell me, which file extensions you need, I'll put them on the list.

Unfortunately you'll have to wait until June, because currently I'm in Florida and enjoy my holidays wink.gif


--------------------
künstliche Intelligenz ist besser als natürliche Dummheit!
rotabench:rotierende Prüfstände nach dem Baukasten-Prinzip
Go to the top of the page
 
+Quote Post
Tomi_Maila
post 16. May 2008, 14:51
Post #3


new Member
*

Group: Members
Posts: 4
Joined: 15.05.2008
Member No.: 57
LV Version: 8.5.1
Zertifizierung: CLAD
LV User seit: 2004



QUOTE(CB @ 15. May 2008, 14:41) *
for sure.

If you can tell me, which file extensions you need, I'll put them on the list.

Unfortunately you'll have to wait until June, because currently I'm in Florida and enjoy my holidays wink.gif

The databases I need to be able to read are of apl, tnb and mtb extensions. Actually I think the extensions are not any standard extensions but as Jet DB doesn't set any requirements for the DB file extension, the application author has decided to go with these extensions.

Enjoy your holidays smile.gif

ps Have you thought of distributing your toolkit as a VIPM compatible package file? It would simplify my life a lot smile.gif I can help you with the packaging if you need...
Go to the top of the page
 
+Quote Post
CB
post 16. May 2008, 16:39
Post #4


proven Member
****

Group: Administrators
Posts: 315
Joined: 16.10.2006
From: Düsseldorf
Member No.: 2
LV Version: current
Zertifizierung: CLA
LV User seit: 2001



QUOTE(Tomi_Maila @ 16. May 2008, 15:51) *
The databases I need to be able to read are of apl, tnb and mtb extensions. Actually I think the extensions are not any standard extensions but as Jet DB doesn't set any requirements for the DB file extension, the application author has decided to go with these extensions.


hmm ... that does not sound like a well known extension to me. Maybe the best way is to add a boolean "check standard file extension (TRUE)", so you can turn off the file extension check if you need.


QUOTE(Tomi_Maila @ 16. May 2008, 15:51) *
Enjoy your holidays smile.gif


for sure I do! I just had a bath in the gulf of mexico wink.gif

QUOTE(Tomi_Maila @ 16. May 2008, 15:51) *
ps Have you thought of distributing your toolkit as a VIPM compatible package file? It would simplify my life a lot smile.gif I can help you with the packaging if you need...

sound like a good idea. What do I have to do to create a VIPM package?


--------------------
künstliche Intelligenz ist besser als natürliche Dummheit!
rotabench:rotierende Prüfstände nach dem Baukasten-Prinzip
Go to the top of the page
 
+Quote Post
Tomi_Maila
post 20. May 2008, 17:54
Post #5


new Member
*

Group: Members
Posts: 4
Joined: 15.05.2008
Member No.: 57
LV Version: 8.5.1
Zertifizierung: CLAD
LV User seit: 2004



QUOTE(CB @ 16. May 2008, 18:39) *
sound like a good idea. What do I have to do to create a VIPM package?

You need a build rule file like the attached one (unzip to see the package file). Easiest way is to open it with OpenG package builder alpha and build openG package using it.

This post has been edited by Tomi_Maila: 20. May 2008, 17:55
Attached File(s)
Attached File  ef_lib_active_vi_toolkit.zip ( 1.09K ) Number of downloads: 421
 
Go to the top of the page
 
+Quote Post
Tomi_Maila
post 21. May 2008, 14:19
Post #6


new Member
*

Group: Members
Posts: 4
Joined: 15.05.2008
Member No.: 57
LV Version: 8.5.1
Zertifizierung: CLAD
LV User seit: 2004



I created an example VIPM package from ADO-Toolkit with OpenG Package Builder. The example is a ZIP file that contains
  1. source folder for ADO source code (LV 8.5 in this case, the file extension requirement removed from Access database connectivity)
  2. resource folder for ADO toolkit icon
  3. built rules folder for VIPM package building rules to be used for example with OpenG Package Builder
  4. built folder with a VIPM package build with OpenG Package Builder from the built rules
Cheers,

Tomi
Attached File(s)
Attached File  ADO_Toolkit_for_VIPM.zip ( 2.51MB ) Number of downloads: 476
 
Go to the top of the page
 
+Quote Post
CB
post 21. May 2008, 16:54
Post #7


proven Member
****

Group: Administrators
Posts: 315
Joined: 16.10.2006
From: Düsseldorf
Member No.: 2
LV Version: current
Zertifizierung: CLA
LV User seit: 2001



QUOTE(Tomi_Maila @ 21. May 2008, 15:19) *
I created an example VIPM package from ADO-Toolkit with OpenG Package Builder. The example is a ZIP file that contains
  1. source folder for ADO source code (LV 8.5 in this case, the file extension requirement removed from Access database connectivity)
  2. resource folder for ADO toolkit icon
  3. built rules folder for VIPM package building rules to be used for example with OpenG Package Builder
  4. built folder with a VIPM package build with OpenG Package Builder from the built rules
Cheers,

Tomi


thanks a lot smile.gif

and what do I have to do to spread that file with the VIPM?

... I'll build the Packages for LV 7.1x after my holidays.

BTW: there is an OS restriction: the ADO toolkit only works on windows


--------------------
künstliche Intelligenz ist besser als natürliche Dummheit!
rotabench:rotierende Prüfstände nach dem Baukasten-Prinzip
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



Lo-Fi Version Time is now: 29.03.2024 - 16:21