System Setups

[Dumbfounded]

Hi Guys,

I wonder if anyone can shed any light on this for me. I've written a database for a client and they are in the process of trialling this to check for glitches and the error messages they are getting are:-

Currently only one person can access the database the error message reads:

"You attempted to open a database that is already open exclusively by admin on machine DM08. Try again when the database is available"

When the checkers are moving from tab to tab they are getting the following message:

"unrecognised database format\\directnas\userdocs\cmd\directdialoguesales database V2.0 Sept.mdb" not sure if this has any repercutions"

At times we are managing to have more than one person on the database, but when entering comments, the database will flash off and on again and all the comments entered are lost

Am I missing something or is this something they need to change at their end. I'm hoping that it's something relatively simple but it wasn't built at their company and thought it might be to do with not opening it exclusively. I've build one for another company and they've installed it with no problems what so ever and it's not been done any differently.

Does anyone know.

Thanks in advance.

Donna x

 

[burrcm]

This usually occurs if you are trying to have multiple users open a single db and they are not all using the same workgroup file and or the same version of Access. Also the name is inappropriate, something like DdsV2Sep.mdb perhaps. Split it into a backend containing the tables, and provide each user with a copy of the frontend which is linked to the backend tables. Much easier to administer and virtually all sharing issues will disappear.

Chris B

 

[RuralGuy]

Are they testing with an MDB or MDE? Have you checked for bogus MISSING references yet?

 

[Dumbfounded]

Hi RuralGuy,

I've sorted out the missing references and I sent them and MDB.

Thanks,

Donna x

 

[burrcm]

<<do I have the split the database or do they have to do it - if I have to do it (which I've never done before) is it easy enough to do?>> This was a private message. No prob with that, but better I think that everyone can see the response as we all want to explore the possibilities don't you think? -

Splitting is easy. Take two new copies of your database. Rename one xxxBE.mdb. Rename the other xxxFE.mdb. Open the BE (backend) copy. Delete everything but the tables. Close. Open the FE (front end) copy. Delete the tables. Any relationships will go here too. Compact. Use the linked table manager to link to the tables in the backend copy. The exact procedure will vary slightly depending on your version. If in doubt, post back. Recreate the relationships if any. Note that the original relationships will be maintained in any pre existing queries, so this step is not critical at this point, but should be done in case of new queries being created. All should now be as it was in the beginning, except that you should not experience problems opening several copies of the FE all linked to the same BE.

Good luck.

Chris B

 

[RuralGuy]

Hi RuralGuy,

I've sorted out the missing references and I sent them and MDB.

Thanks,

Donna x

Thanks for posting back Donna.