NauticalGent
Ignore List Poster Boy
- Local time
- Today, 09:17
- Joined
- Apr 27, 2015
- Messages
- 6,754
Hello SportsFans,
I have inherited an application that is a real piece of work. The original author was VBA-centric and pretty much used Access for tables and forms only. The others that can after him were more Access oriented and used sites, this one included, to figure out how to make changes/updates.
One of the "updates" was the introduction of the code on this thread:
http://www.access-programmers.co.uk/forums/showthread.php?t=217400&highlight=Hide+access+window
Not a big fan of it and I intend to take it out - but for now I have a more pressing issue. Because of the 'lock-down' nature of this code, users can only view one form at a time (another issue I will tackle). There are times they need to see other data and instead of closing the current form and opening the one they want, they open the DB again using the FE on their local computer (I forgot to mention the DB is split).
I have been there for 2 weeks and I have had to do "surgery" at least once due to corrupted data. I have advised the users not to do this, but there are some rebels out there and I don't like to leave things to chance...
What I would like to do is put in some code that detects if the DB is already open and if so, quit the newly open instance but keep the other instance open.
As always, thanks in advance!
I have inherited an application that is a real piece of work. The original author was VBA-centric and pretty much used Access for tables and forms only. The others that can after him were more Access oriented and used sites, this one included, to figure out how to make changes/updates.
One of the "updates" was the introduction of the code on this thread:
http://www.access-programmers.co.uk/forums/showthread.php?t=217400&highlight=Hide+access+window
Not a big fan of it and I intend to take it out - but for now I have a more pressing issue. Because of the 'lock-down' nature of this code, users can only view one form at a time (another issue I will tackle). There are times they need to see other data and instead of closing the current form and opening the one they want, they open the DB again using the FE on their local computer (I forgot to mention the DB is split).
I have been there for 2 weeks and I have had to do "surgery" at least once due to corrupted data. I have advised the users not to do this, but there are some rebels out there and I don't like to leave things to chance...
What I would like to do is put in some code that detects if the DB is already open and if so, quit the newly open instance but keep the other instance open.
As always, thanks in advance!