Split Database Question

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Maldo - 17 Apr 2008 17:34 GMT

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 Options>Advanced 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!!!

Reply to this Message

Chris O'C - 17 Apr 2008 17:48 GMT

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

>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
[quoted text clipped - 10 lines]
>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!!!

Reply to this Message

Maldo - 17 Apr 2008 22:26 GMT

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 and
[quoted text clipped - 18 lines]
> >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!!!

Reply to this Message

Chris O'C - 18 Apr 2008 14:48 GMT

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

>Chris,
>Thanks for the repsone. It makes perfect sense. Sorry but I am new to
[quoted text clipped - 3 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

Reply to this Message

Maldo - 18 Apr 2008 15:51 GMT

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

Reply to this Message

George Nicholson - 18 Apr 2008 16:36 GMT

> 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/features/msaccess/article.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.

Signature

HTH,
George

> 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
[quoted text clipped - 21 lines]
>> >> splitting the database. Place a copy of the front end on every user's
>> >> PC

Reply to this Message

Maldo - 21 Apr 2008 16:33 GMT

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.

> > what would be the best way to distribute the FE to my users outside of
> > email...
[quoted text clipped - 40 lines]
> >> >> splitting the database. Place a copy of the front end on every user's
> >> >> PC

Reply to this Message

Chris O'C - 18 Apr 2008 16:42 GMT

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

>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
[quoted text clipped - 6 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

Reply to this Message

Maldo - 21 Apr 2008 16:38 GMT

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,

> 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
[quoted text clipped - 13 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

Reply to this Message