Error DLL

[Guest]

After a total database collapse and having to recover the data all the forms
and reports were lost. The original database was created in an earlier
version of Access. Using Access Pro the database was migrated to Access
2003. I recreated forms and reports including a main and sub switchboards.
The database resides on the computer with Access 2003. A remote computer on
a MS network was using the old version of the switchboard just fine. Now
however, then the remote computer pulls up the database the error occurs.
The remote computer is running Access 2000. The actual line of code in the
VB is as follows;

Set con = Application.CurrentProject.Connection

I think(I know thats bad but...) the older version of Access may not be able
to read some new code or something. Any help or seggestions will be
appreciated. Maybe I need Access 2003 runtime? Anyway thanks for reading.

 

[Guest]

Hi.

After a total database collapse and having to recover the data all the forms
and reports were lost.

I have a pretty good idea why. The #1 cause of Access database corruption
is multiple users accessing a single database file from across the network.
Microsoft recommends splitting the database into a back end and front end,
with the tables and relationships in the back end stored on the networked
server, and a copy of the front end, with all the other objects (forms,
queries, reports, modules, et cetera), stored on each workstation. For more
information on split databases, please see the following Web page:

http://www.Access.QBuilt.com/html/gem_tips.html#SplitDB

then the remote computer pulls up the database the error occurs.
The remote computer is running Access 2000. The actual line of code in the
VB is as follows;

Set con = Application.CurrentProject.Connection

This line of code will work in Access 2000 as long as the con variable is
dimmed as an Object. Since the code works in Access 2003, presumably it's
set correctly.

However, the remote computer should not be "reading" code on this computer.
If the database were split, the workstation with Access 2000 would have the
front end residing on that workstation and not have to deal with a foriegn
computer's configuration or DLL version incompatibilities.

Look at the ADO object library version. Is it 2.1? It needs to be if
Access 2000 is going to be using it. Make sure you have the latest version
of MDAC (ver. 2.8 SP-1) and Jet 4.0 SP-8 installed on all computers that
access the database. Please see the following Web pages for downloads:

http://msdn.microsoft.com/data/mdac/default.aspx

http://msdn.microsoft.com/data/downloads/updates/default.aspx#jet

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)

- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts as "Answers,"
so that all may benefit by filtering on "Answered questions" and quickly
finding the right answers to similar questions. Remember that questions
answered the quickest are often from those who have a history of rewarding
the contributors who have taken the time to answer questions correctly.

 

[TBATEL]

Thanks

Thanks Gunny for the information. The con is dimmed as an object. I tried to split the database and the split was successful. The same error occured on the set con as before even though the front end was on the other computer. I need to correct an error from my previous post. The database is a 2000 database but all code changes are occuring with 2003. Should I destroy the switchboard and recreate it on the other computer? The database window arrives and all the forms except the switchboard work fine. But the user needs the switchboard.