Split database - Disk or Network Error 1

[jherl]

I have an Access 2002 split database application and I am using the MS Access workgroup file for security. The back end component and the workgroup file reside on a network system running XP that is accessible by all users. I have no problems when one user accesses the database. When a second user attempts to access the database I am getting either a 'Disk or Network error' or a (-1104) error message. I have check that the back end and front end of the application are defined as shared access with record level locking and the code does not impose any higher level of locking. I have checked that the shared folder on the network system containing the back end component is not a read only folder, all users have read, write, create and modify permission on the shared folder....

I know this is not a hard thing to do, but somewhere I have messed things up...PLEASE HELP !

Thanks -
Jennifer

 

[scking]

You should always check out the Microsoft Knowledgebase for errors like this. The first url describes the problem and the second talks about the fix in Access 2000 SP3.

http://support.microsoft.com/default.aspx?scid=kb;en-us;304548&Product=acc

http://support.microsoft.com/default.aspx?scid=kb;en-us;326605&Product=acc

---------------------
scking@arinc.com
---------------------

 

[vbajock]

Where is the front end located?

 

[jherl]

Thanks for the direction. Both these articles refer to Access 2000. Unfortunately, I have been able to duplicate the problem without the Access 2000 component. In other words, the backend is Access 2003 and the front end is Access 2003, both on Windows XP and all components current on SPs.

 

[TomCarnahan]

scking ----

Many thanks! ... this is exactly the problem I have been having at work. The LAN people have been dragging their feet on installing new service packs.



--- Tom

 

[oharab]

jherl,
As VBAjock says, where is your front end? This must be on the local machine and not stored on a network folder.
If you are still getting problems, then you need to start checking the LAN. It has been said that MS should package Access as a stress tester as it will find any weaknesses in your LAN. Make sure all the network cards are working properly, try chaning them if you can. Try different computers roound the office, starting as close to the server (cabling wise) as possible and moving out.
Ask your network team to look for packet collisions on the network, this could upset access long enough to think there's a problem.
My final thought would be to compact and repair your back end, or even import all it's data into a fresh, clean database.

Good luck

Ben

----------------------------------------------
Ben O'Hara

http://www.RobotParade.co.uk

"Where are all the stupid people from...
...And how'd they get so dumb?"

NoFX-The Decline
----------------------------------------------

 

[jherl]

Thanks for the suggestions. I the front end is on workstations in the office running Win 2K w/ Access 2000 or Win XP w/ Access 2003. All are updated with latest service packs - both Windows and Access.

I did run a test last week where I was just checking the network. I had several of the workstation in the office mount the drive from the back end server and then simultaneously open a simple txt file. I had no problems with this, so I eliminated the simple network configuration as the problem. ( Maybe I was a bit to quick in my thinking there, but I assumed I was not having connectivity / network issues if I could accomplish this task ). I don't believe I have a simple database problem becuase things work beautifully when only one user access the database across the network. I think I am having a complex problem that involves network and database, like a configuration setting somewhere ( either db or network ) that is not set. I have checked that the folder where the back end resides on the server is shared with all available permissions allowed for all users.

Please keep the ideas coming. I am grateful for the assistance !
Jennifer

 

[TomCarnahan]

My problem with this came right after a weekend in which they uploaded some patches (or who knows what). My backup copies and copies restored from the LAN backup don't work.

When I go into the VB Editor and look at references, the system decided to select 4 new DLL's that I have no idea what they are for. When I try to de-select them, the system tells me I can't do that. When I try to compile my code, it says it 'Disk or Network error'.

One of the friendly LAN Admin types and I are trying to locate a PC that didn't get the update to validate our theory that the weekend update did it to me.

I looked at the MS KB article and their proposed solution. Because of the snail pace of incorporating new service packs in a secure environment (we are on SP-1), get that pack installed won't happen any time soon (even though SP-3 has been out for over a year).

The other solution, copying all the code to text files for 50+ forms and reports; 20+ modules will require a lot of work.

Does anyone have an idea of how to use VB extensibility code to automate the code export?

Thanks!

--- Tom