Moving MDB to another domain

[SimonB1978]

Hi,

Here is the situation: the IT department moved all of the users computer to a different domain the past week-end. Domains A contains the servers and domain B contains the users' computers. Before that, we only had one domain.

The problem: a group of users have to use a MDB which is located on a server. Nothing is installed client-side. Before the domain move, they could be more than one person using it. Now, only one person can open the MDB at a time. Other users cannot open it while it is open by someone else. As soon as it is "closed" another can open it.

Is it related to the domain thing? Is there any way to go around this?

Thank you very much!

Simon B.

 

[Dairy Farmer]

Sounds like you never slit the app into a Front End and Back End.

The FE resides on every client pc that uses the app and has all the forms, queries, reports, moduals, macros and VBA. The BE tables are linked in the FE.

The BE resides on the file server and contains only the tables (i.e. just the data).

 

[SimonB1978]

I know how the app should have been developped (was not even here at the time).

However, the purpose is not to redesign it but having it work like it used to in the last 8 or so years...

 

[Dairy Farmer]

It will take about 5 minutes to split the db and compile it as an MDE.
Then rename the mde to mdb so as not to loose shortcuts. Users will not be able to edit it.

MDB is dangerous as users can change it.

This may solve the problem.