Help Urgent connection issue

access 97 v's 2000

[SuzyUK]

Hi I've to demo a site tomorrow, and it's suddenly stopped working!

I using an access 97 database with a dsn-less connection, all was fine until this morning and it's now reporting errors site wide

Phoned web host and they set up a DSN name but I still couldn't connect with this

They say I need to upgrade to Access 2000? anyone else heard this, (this is a voluntary project and I don't need to upgrade unless necessary...)

I've repaired, compacted and re-uploaded database in case it had been corrupted somehow...

Any ideas or advice?

Suzy

[edit]
not so urgent now, I changed to an OLEDB connection had that has solved it for now..

but I would still be interested in hearing if anyone else has had compatibility issues between Access97 and 2000, thank you
[/edit]

[korkus2000]

Are you using a jet provider? If so you need to use the 4.0 version in your code because their access 2000 uses it. You can use a 97 database.

[Woz]

You definitely do not need to update to Access2000. As Korkus2000 says you need to use the correct Jet connection for the server, or use something like

Driver={Microsoft Access Driver (*.mdb)}; DBQ=C:\PATH\database.mdb;Uid=;Pwd=;"

which seems to work with me, although may be a little slower I understand.

When Access 2000 first came out there were a lot of concerns that it ran slower online than Access 97 so I did not upgrade. I really don't know whether this still holds true but I have stuck with Access 97 for that reason and also to remain as compatible with as menay people as possible. It is surprising the number of people still using Office 97 and even Office 95. I set by lowest denominator as Office 97 and have stuck there, even to converting Access 2000 databases that I receive back to 97 before working with them.

Seems to work for me.

Onya
Woz