Data Control Problem!!

[wfs1979]

I set the my database name in the data control properties, in result when the application is ran i recieve this error:

Unrecognized database fromat 'FILE PATH & NAME'

Heres the thing that confuses me, if i create a .mdb file using Access 2000 it doesn't work, but if i set the database name to a file that was created with access '97 it works?? Should i uninstall Access 200 & install '97???

[HunterMcCray]

Originally posted by wfs1979
I set the my database name in the data control properties, in result when the application is ran i recieve this error:

Unrecognized database fromat 'FILE PATH & NAME'

Heres the thing that confuses me, if i create a .mdb file using Access 2000 it doesn't work, but if i set the database name to a file that was created with access '97 it works?? Should i uninstall Access 200 & install '97???

Access 2000 has a quite different internal structure than Access 97. I am in the process of attempting to migrate to Access 2000 from 97 in my own App. I believe you have to change your references from DAO 3.51 to DAO 3.6, but I have read that there are some real problems with this....I sometimes wonder why we bother to "Upgrade", only seems to create more problems....

Hunter

[P.S.W.]

Try using the ADO control with Jet 4.0 - this should let you use Access 2000 without any problems.

[wfs1979]

Using just the data control you can use a .mdb file from access 2000, you create the database in access 2000, save it and under(i think) tools-->database utilities-->"convert to previous version of access",and (i believe)you have to save the database under another name. [dont hold me to it though]LoL. I'll try out what you guys suggested. Thanks for your repsonces!


--wILL-->

[honeybee]

The ideal solution is this:

If you are using a Data Control, you cannot directly access any Access 2000 database.

If you maintain your database in Access 2000 and keep converting back to Access 97, it becomes irritating at times.

So keep the database in 2000 format, use ADO to access it and assign the ADO Recordset as the recordsource of the Data Control you are using.


All this is borrowed knowledge, but will be useful to you all. I have never yet used the data control, but I think it's fairly easy to do.

wfs1979, it means that you cannot hardcode the database name in your Data Control properties. The Data Control properties need to be set at runtime depending upon the ADO recordset you are using.

As always, hope it helps!