T
Tom Wickerath
Hi Wael,
You cannot do this. As soon as the first user opens any object in design
view, their access (no pun intended) will be promoted to exclusive, thus
locking out others. I believe Access 97 was the last version that allowed
simultaneous users to have different objects in the same database opened in
design view.
Your best bet is to split the application into a front-end (FE) and back-end
(BE) databases. Distribute a copy of the FE to each developer, to be placed
on their local hard drive. Now, each developer will be able to open any
object (other than the shared tables in the BE database) in design view. You
can import the changes later on, in a new master FE database.
Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
You cannot do this. As soon as the first user opens any object in design
view, their access (no pun intended) will be promoted to exclusive, thus
locking out others. I believe Access 97 was the last version that allowed
simultaneous users to have different objects in the same database opened in
design view.
Your best bet is to split the application into a front-end (FE) and back-end
(BE) databases. Distribute a copy of the FE to each developer, to be placed
on their local hard drive. Now, each developer will be able to open any
object (other than the shared tables in the BE database) in design view. You
can import the changes later on, in a new master FE database.
Tom Wickerath
Microsoft Access MVP
https://mvp.support.microsoft.com/profile/Tom
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________