error 2486

[KimberTech]

At wits end, any and all suggestions considered.

I am a hardware/network tech, not Access...so I am working with another consultant who is doing her bit. I am trying to help as much as possible by eliminating hardware/OS/settings issues.

This is the latest error plaguing the MDB. If you need more information about what is being accessed and what is connected to what, I can find out.

Originally Windows 98SE two machines P2P network. Has been IPX and TCP protocol.
Machines share a DB on machine two....direct network shortcut, no permissions problems. Hardware checks out.

Upgraded to Windows XP Pro SP2 to address lagging and memory issues....no other apps fail no other network errors including printing etc.

The errors have been everything from out of memory ...now fixed since upgrade... to the newest complete hang of the whole app and task manager out with error 2486.They occur on both the host machine and the machine that accesses through the network. The problems definitely occur when the queries are running "deep in the guts" of the database itself.
Another issue has been opening a form in design view which more often than not will produce an error also.

My intuition tells me this is settings/software or database corruption. I have advised several things including a repair and a compact...
Currently going through a list of software installed on the host machine that might be causing the errors.

ANYONE?

Thanks ahead for any and all consideration..

K

 

[hneal98]

I would bet that your intuition of database corruption would be correct. If the repair/compact does not work, you may just have to recreate the database.

One thing I have been able to do successfully is create a new database and then import the objects (Tables, forms, queries, etc.) from the old database.

However; since this sounds like a major problem database, you might want to just import some parts at a time and run tests on it.

Don't know if this helped much, and others may have other opinions.

 

[JoeAtWork]

Something that has often saved a corrupt database (when Compact & Repair didn't help) is to open the MDB using the "decompile" command line argument. At the command prompt, run the following (changing the paths to your situation):

"C:\Program Files\Office2000\Office\MSACCESS.EXE" /decompile "C:\Database\MyDatabase.mdb"

When it's decompiled, go into a VB window and compile all modules again (your programmer should know how).

If it's not been done already, the database should be split to a front-end/back-end solution. This keeps the data safe from corruption caused in code.

 

[KimberTech]

Thank you for the responses.

Interestingly enough, the database was reindexed and then the form in question was revised so that the refresh could take properly.

For future reference, it had to do with a calculation in a text box in a complicated form deep within the database.
Not always an issue, and not on all machines....but apparently a known issue that is not well documented.

Hope this helps someone in the future.

K