Test if form is open between users

[Paintballlovr]

Not sure if this should be in forms or programming. I found a similar post to what I'm asking in programming, but it's not working for my issue. What I'm trying to do is create a check between multiple users who are trying to go into the same form. I want the second person to also get into the form, but I need some other items to fire if they're not the first one in. The code works fine for a single user, but when a second user opens the form, the other items don't fire. I'm guessing it's something to do with the users being on different sessions, so I'm not sure if there is something I can do "globally" so that the second users session sees that the first user has the form open. Here is the code I'm using:

If SysCmd(acSysCmdGetObjectState, acForm, "worklist j-l") = acObjStateOpen Then

[ranman256]

Each person should have their own copy of the program (frontend) of a split db
with the tables on the backend of a split db.
Then everyone can be in the 'same' form. Otherwise you can get errors.

[Paintballlovr]

Does that mean it can't be done with two users accessing the same instance of the front end via shortcuts? I understand this isn't the ideal way to do it, but I need to know what my options are.

[Missinglinq]

Having multiple users sharing a single Front End, on a network drive, is a sure fire way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior!

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past nine years have seen literally dozens and dozens of reports of split databases, using links to a single Front End, causing these kinds of problems, as well as massive data loss! The really insidious thing is that this kind of setup can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

You simply have to put a copy of the Front End on each user's PC!

Linq ;0)>

[Paintballlovr]

The only reason I haven't pursued that with all of the databases I have been tasked with maintaining is the nightmare of maintenance. I seem to get fairly regular requests to make changes and not being in IT, I don't know how/if I could push updates out to the users, so that leaves me with visiting each one to install the change. Taking that x almost 40 databases x a potential user pool of over 300 users = I need a raise Jokes aside, I did realize that local copies might be the only solution, just maybe not desirable. Not to hijack my own post, but if there is some instruction I can get on deploying new versions to the users, that might kill two birds with one stone.

[ranman256]

You could write vba code that pulls the list of users from a table,
then copy the file to each user's work folder.

[Missinglinq]

There are a bunch of hacks out there for doing this automatically. Here are two:


http://www.utteraccess.com/forum/Aut...E-t135969.html

http://www.rogersaccesslibrary.com/f..._topic409.html

You can also google using the terms

front end updater

and you'll get a bunch of hits, some free and some commercial.

Linq ;0)>

[orange]

Totally agree with linq -split your database into FE/BE.
There are many front end updaters.
Here's a video of one, but there are others.

Here are some performance tips for your review.
http://www.granite.ab.ca/access/performancefaq.htm
http://www.fmsinc.com/microsoftaccess/DatabaseSplitter/
http://www.fmsinc.com/microsoftacces...ddatabase.html
http://msdn.microsoft.com/en-us/libr...ice.12%29.aspx

Good luck

[June7]

For discussion on methods of distributing frontend updates, review https://www.accessforums.net/code-re...end-33331.html

[Paintballlovr]

The conversion has been made. Each user now has their own copy of the front end.