If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Split Database Question
I have a Multiuser data entry mdb (built in Access 2003) split between FE and
BE. Both FE and BE reside on network directory. Each user has read/write access to the network drive. I have a start up form with the datasource being a table linked to the BE. My Start up options have all menus and toolbars turned off. Under my OptionsAdvanced tab the default open mode is set to Shared for FE and BE mdb's. Record locking is set to No Locks. Some of the users have seen this message pop up at start up -- "You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later." I have a moderate level of vba event procedures behind the form including a MouseHook function that disables the mouse wheel to prevent users from scrolling through existing records. I don't think there is anything wrong with my code so I don't know where else I can begin trouble shooting this issue as it only seems to be happening for a few users. Can anyone offer some guidance? Thanks!!! |
#2
|
|||
|
|||
Split Database Question
By having everyone share the same front end file, you defeat the purpose of
splitting the database. Place a copy of the front end on every user's PC and have each user only open their own copy. They will each have exclusive access on their own copy whenever needed. Chris Microsoft MVP Maldo wrote: I have a Multiuser data entry mdb (built in Access 2003) split between FE and BE. Both FE and BE reside on network directory. Each user has read/write access to the network drive. I have a start up form with the datasource being a table linked to the BE. My Start up options have all menus and toolbars turned off. Under my OptionsAdvanced tab the default open mode is set to Shared for FE and BE mdb's. Record locking is set to No Locks. Some of the users have seen this message pop up at start up -- "You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later." I have a moderate level of vba event procedures behind the form including a MouseHook function that disables the mouse wheel to prevent users from scrolling through existing records. I don't think there is anything wrong with my code so I don't know where else I can begin trouble shooting this issue as it only seems to be happening for a few users. Can anyone offer some guidance? Thanks!!! -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#3
|
|||
|
|||
Split Database Question
Chris,
Thanks for the repsone. It makes perfect sense. Sorry but I am new to working with a split a database. I asked the user to put a copy of the FE on their local machine and everything works fine. Thanks again!!! "Chris O'C via AccessMonster.com" wrote: By having everyone share the same front end file, you defeat the purpose of splitting the database. Place a copy of the front end on every user's PC and have each user only open their own copy. They will each have exclusive access on their own copy whenever needed. Chris Microsoft MVP Maldo wrote: I have a Multiuser data entry mdb (built in Access 2003) split between FE and BE. Both FE and BE reside on network directory. Each user has read/write access to the network drive. I have a start up form with the datasource being a table linked to the BE. My Start up options have all menus and toolbars turned off. Under my OptionsAdvanced tab the default open mode is set to Shared for FE and BE mdb's. Record locking is set to No Locks. Some of the users have seen this message pop up at start up -- "You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later." I have a moderate level of vba event procedures behind the form including a MouseHook function that disables the mouse wheel to prevent users from scrolling through existing records. I don't think there is anything wrong with my code so I don't know where else I can begin trouble shooting this issue as it only seems to be happening for a few users. Can anyone offer some guidance? Thanks!!! -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#4
|
|||
|
|||
Split Database Question
Don't let everyone else share the same front end file. The most important
reason for splitting the database and giving everyone their own copy of the front end is to avoid corrupted database files. Chris Microsoft MVP Maldo wrote: Chris, Thanks for the repsone. It makes perfect sense. Sorry but I am new to working with a split a database. I asked the user to put a copy of the FE on their local machine and everything works fine. Thanks again!!! By having everyone share the same front end file, you defeat the purpose of splitting the database. Place a copy of the front end on every user's PC -- Message posted via http://www.accessmonster.com |
#5
|
|||
|
|||
Split Database Question
Thanks Chris for your advice. While on this topic, what would be the best
way to distribute the FE to my users outside of email. I would like to be able to make sure that the users always have the most updated version of the FE on their local PC each time the submit their data. "Chris O'C via AccessMonster.com" wrote: Don't let everyone else share the same front end file. The most important reason for splitting the database and giving everyone their own copy of the front end is to avoid corrupted database files. Chris Microsoft MVP Maldo wrote: Chris, Thanks for the repsone. It makes perfect sense. Sorry but I am new to working with a split a database. I asked the user to put a copy of the FE on their local machine and everything works fine. Thanks again!!! By having everyone share the same front end file, you defeat the purpose of splitting the database. Place a copy of the front end on every user's PC -- Message posted via http://www.accessmonster.com |
#6
|
|||
|
|||
Split Database Question
what would be the best way to distribute the FE to my users outside of
email... Rather than pushing updates, the general consensus seems to be to have the user's machine do a version check against the "current" copy on the network and pull down an update if needed. Details of exactly how to do that may vary a bit. Auto FE Updater http://www.granite.ab.ca/access/autofe.htm Even if you don't use his (free) tool, Tony's site provides a lot of good ideas and links. Nowadays I use a variation from one of those links http://www.databasejournal.com/featu...le.php/3286111 because I ran into one client where .exe files aren't allowed on the network (i.e., they are periodically deleted), so I couldn't use Tony's app. -- HTH, George "Maldo" wrote in message ... Thanks Chris for your advice. While on this topic, what would be the best way to distribute the FE to my users outside of email. I would like to be able to make sure that the users always have the most updated version of the FE on their local PC each time the submit their data. "Chris O'C via AccessMonster.com" wrote: Don't let everyone else share the same front end file. The most important reason for splitting the database and giving everyone their own copy of the front end is to avoid corrupted database files. Chris Microsoft MVP Maldo wrote: Chris, Thanks for the repsone. It makes perfect sense. Sorry but I am new to working with a split a database. I asked the user to put a copy of the FE on their local machine and everything works fine. Thanks again!!! By having everyone share the same front end file, you defeat the purpose of splitting the database. Place a copy of the front end on every user's PC -- Message posted via http://www.accessmonster.com |
#7
|
|||
|
|||
Split Database Question
Use the Auto FE Updater http://www.granite.ab.ca/access/autofe.htm. Every
time a user opens the front end, it will check for the latest version and update it automatically. Chris Microsoft MVP Maldo wrote: Thanks Chris for your advice. While on this topic, what would be the best way to distribute the FE to my users outside of email. I would like to be able to make sure that the users always have the most updated version of the FE on their local PC each time the submit their data. Don't let everyone else share the same front end file. The most important reason for splitting the database and giving everyone their own copy of the [quoted text clipped - 10 lines] By having everyone share the same front end file, you defeat the purpose of splitting the database. Place a copy of the front end on every user's PC -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#8
|
|||
|
|||
Split Database Question
Thanks for the info. After reveiwing the several methods out there I think I
am gonna try and implement the Database Journal version you are using. Thanks for your help. "George Nicholson" wrote: what would be the best way to distribute the FE to my users outside of email... Rather than pushing updates, the general consensus seems to be to have the user's machine do a version check against the "current" copy on the network and pull down an update if needed. Details of exactly how to do that may vary a bit. Auto FE Updater http://www.granite.ab.ca/access/autofe.htm Even if you don't use his (free) tool, Tony's site provides a lot of good ideas and links. Nowadays I use a variation from one of those links http://www.databasejournal.com/featu...le.php/3286111 because I ran into one client where .exe files aren't allowed on the network (i.e., they are periodically deleted), so I couldn't use Tony's app. -- HTH, George "Maldo" wrote in message ... Thanks Chris for your advice. While on this topic, what would be the best way to distribute the FE to my users outside of email. I would like to be able to make sure that the users always have the most updated version of the FE on their local PC each time the submit their data. "Chris O'C via AccessMonster.com" wrote: Don't let everyone else share the same front end file. The most important reason for splitting the database and giving everyone their own copy of the front end is to avoid corrupted database files. Chris Microsoft MVP Maldo wrote: Chris, Thanks for the repsone. It makes perfect sense. Sorry but I am new to working with a split a database. I asked the user to put a copy of the FE on their local machine and everything works fine. Thanks again!!! By having everyone share the same front end file, you defeat the purpose of splitting the database. Place a copy of the front end on every user's PC -- Message posted via http://www.accessmonster.com |
#9
|
|||
|
|||
Split Database Question
Thanks for your help Chris. After reviewing some of the several methods
available I am gonna attempt the version in the Database Journal that George Nicholson mentioned earlier in this thread. Thanks, "Chris O'C via AccessMonster.com" wrote: Use the Auto FE Updater http://www.granite.ab.ca/access/autofe.htm. Every time a user opens the front end, it will check for the latest version and update it automatically. Chris Microsoft MVP Maldo wrote: Thanks Chris for your advice. While on this topic, what would be the best way to distribute the FE to my users outside of email. I would like to be able to make sure that the users always have the most updated version of the FE on their local PC each time the submit their data. Don't let everyone else share the same front end file. The most important reason for splitting the database and giving everyone their own copy of the [quoted text clipped - 10 lines] By having everyone share the same front end file, you defeat the purpose of splitting the database. Place a copy of the front end on every user's PC -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
Thread Tools | |
Display Modes | |
|
|