Edit Access while open? 1

[mattloflin]

HEy guys I have a database ("Purchase") and it's MDE is on everyones desktop the database ("Database") is on the network.

The "Database" is a linked database.

I have the MDB on the network too and everytime I open it while someone else has the MDE open it states that I don't have exclusive rights to the database.

Does that mean I don't have exclusive rights to the "Database" or "Purchase" ? cause no one else has the MDB open except me.

Basically I want to make changes to the .MDE while they have the .MDB open. Is that not feasible with the linked database?

- Matt

"Never Give a Sword to a Man Who Can't Dance

 

[Pampers]

quote:

Microsoft Access MDE File Format
The MDE file format is a special extension of the standard Microsoft Access MDB format, and is used to distribute an application. An MDE file compiles all of the modules, removes all editable source code and compacts the database. The resulting MDE file allows the database users to perform normal database operations, however it prohibits any changes from being made to the objects that support, or the code that runs the application.

http://www.databasedev.co.uk/microsoft-access-mde.html

Pampers
Keeping it simple can be complicated

 

[boblarson]

If you are talking about not being able to make changes to the backend database while someone is in it, this is true if you are changing anything that someone has open. You can add tables since no one could possibly be in it at the time, you can delete any tables or fields in tables if those tables are not currently being used by someone.

However, the best thing to do for changes to the backend is to make sure that everyone is out of their frontends before you need to do anything to it.


Bob Larson
A2K,A2K3,A2K7,SQL Server 2000/2005,Crystal Reports 10/XI,VB6, WinXP, and Vista
Free Quick Tutorials and Samples:

http://www.btabdevelopment.com

 

[mattloflin]

so I guess there isn't a way...

thanks guys!

Just have to close everyone out before editing..

no bueno but sometimes that's how it is

- Matt

"Never Give a Sword to a Man Who Can't Dance"

Win 98/2000/2003 Server/XP/Vista, Active Directory
- VB6, Access, Excel, HTML
- Dreamweaver, Fireworks
OS X 10.4/10.5
Linux Red Hat, Xubuntu, Ubuntu

 

[Pampers]

Yes, basically you have to close out users...
But this doesn't have to be a problem. You can create a new front end and distribute it when users are closing there app or close them out automatically at the end of the day, or close them out directly with after you give them a message.



Pampers
Keeping it simple can be complicated

 

[boblarson]

Pampers wrote: " You can create a new front end and distribute it when users are closing there app or close them out automatically at the end of the day, or close them out directly with after you give them a message."

Or you can use a tool like I have that will enable auto frontend updating where you make changes to the frontend master and then when the user opens their current version it tells them that it is out of date, closes automatically, deletes the old frontend, copies the new frontend to their computer and then automatically reopens for them. You can get the tool here:

http://www.btabdevelopment.com/main/AccessTools/tabid/78/Default.aspx

(Remember to download and read the documentation too).

But, as for the backend, you could have a hidden form with a timer that searches for a boolean flag you set in the backend and if true it tells the user that it has to close in, say two minutes (to give them time to finish anything they are working on), and then quits the app when the two minutes are up.


Bob Larson
A2K,A2K3,A2K7,SQL Server 2000/2005,Crystal Reports 10/XI,VB6, WinXP, and Vista
Free Quick Tutorials and Samples:

http://www.btabdevelopment.com

 

[Pampers]

Tnx Bob for that link, I'll give it a try.

At the moment I'm testing this application for distributing new FE's.

http://www.frontend-loader.com/support.php

Pampers
Keeping it simple can be complicated