Creating a Temporary Instance of the Database?

[XelaIrodavlas]

Hi all,

I am looking for some advice/discussion. We are planning to migrate our access databases to a server to be accessed by a remote desktop application. I won't bore you with the details but the point is this allows a licensed number of users to open the database without having MS Access installed on their machines.

My concern is, using a remote desktop gateway means opening the front in much the same way as if multiple users opened it from the same desktop... The record locking should be able to handle it, but in the past I have encountered errors and corruption when working this way.

(At present I have always had my users keep private copies of the front end and send out updates as required)

So I was wondering if there are going to be issues using this method going forward, and if so would I be able to write some code that opens a separate instance of the chosen access database, rather than opening the original copy itself? in other words I would create a temporary, carbon copy, that will handle record locks etc, but that wont affect the original database should any corruption or weirdness occur...

Does anyone know of a good resource to get me started, or do I even need to bother?? I might be over-thinking it!

Any thoughts and discussion welcome, has anyone been through this before? what did you do?

Many thanks,

 

[jdraw]

??? for clarification

Are you talking about a split database ---1 backend with tables/data and multiple copies of the front end(1 for each user)???

see http://www.fmsinc.com/microsoftaccess/DatabaseSplitter/

http://www.fmsinc.com/microsoftaccess/Performance.html

 

[XelaIrodavlas]

Yep all our databases are split with Back end(s) sitting on our network drives.

thanks for the links I can see i'll have a lot to think about!

 

[Minty]

Use Access Runtime (Free) and give each user there own remote desktop login. They are then all running a unique version.