Problem with two instances of a FE open at same time?

[twgonder]

@ Welshgasman #15. Well, I did work in that environment. It was handled differently and mentioned in post# 8.


Also, I spent a lot of time with instances, and reported in at least one thread here all the problems that were going on and how Access got very confused as to which instance code was running for.
allenbrowne didn't get very deep into the "feature" and no one on this forum had an answer to what was going on:
https://www.accessforums.net/showthr...light=instance

On the last round of minis that I worked on, one would just login again to another instance of the "data account" (where all the client data was). There was no need to shutdown the open session, and the O/S never corrupted data between login sessions unless something very bad happened outside normal operations. There was no need to make duplicate copies of the application software just to start another instance. We had dozens of workers all working in the same "form" (called data entry screen) at the same time for the same data account without problems for decades. Before that, in college, we had hundreds of students all running the same program at the same time on the mainframe. It's not a new concept, except to MS. Had the MS Access team looked around when they started with the toy db for one-up users, they would have realized the need to shadow copy the .accdx file, or some other sandbox method, so that multiple instances didn't become a source for corruption.

Building an instance for one form, even if it worked okay, would then logically require the menu application to be able to instance any form (or report) that the user might want to use in duplicate+. Oh boy, let's not go there seeing that it can't work properly with just one form opening multiple times.

[ArviLaanemets]

Can you explain that a bit more (or give a link)?

1. In your LAN, on some network resource accessible to all users you have saved a BE file, where all data needed by all users is stored;
2. Users access/update the data in BE file via FE file, which is used to connect only to this BE file by this user. FE files may be identical (i.e. several users can have copy of same FE file to work with, or they may differ for different users (like some users need access to production info only, and other ones to financial info only, and other to storage info, etc.). FE file may be stored in user's computer, or on network resource, or in user's Terminal server profile;
3. Both BE file, and FE file must be in same LAN - Access doesn't cope perfectly with data moving over WWW (But I have worked with LAN, where several local networks in different countries are connected to single LAN, and there Access didn't have any problems.);

Now about remote access. User connects remotely into his/her LAN, and logs into his/her computer in case this is allowed, or into his/her TS profile. And runs his/her FE from there. Over WWW, only keyboard/mouse actions, and display picture are moved. For Access, this is same as the user works from LAN locally. And it will be easier to manage, when all users who may need to work with database remotely, do this always from TS profile (both working remotely and locally), and from same laptop used by this user.

[June7]

"BE files may be identical" - did you mean FE?

[ArviLaanemets]

"BE files may be identical" - did you mean FE?

Sorry! It was a typo!

[CJ_London]

Also, I spent a lot of time with instances, and reported in at least one thread here all the problems that were going on and how Access got very confused as to which instance code was running for.

only because those instances were referencing subs/functions/global variables in a standard module. If you had used class modules it would not be a problem. If you haven't done so already, you also probably need to learn and understand collections and dictionaries

[Gicu]

Sorry for the delay, my launcher is intended to be used for version deployment, it will open the selected FE based on a certain path (usually the launcher is placed in the same local folder as the FE). So if you need two instances of the FE you would simply make another subfolder and place a copy of the FE and the launcher there and make a shortcut to the desktop.
Cheers,