can't open front end when back end in use

[pat67]

I am new to this idea of using a front end/back end. But if I am
working on the back end, no one can open the front end. Is there any
way around this? Thanks

 

[John W. Vinson]

I am new to this idea of using a front end/back end. But if I am
working on the back end, no one can open the front end. Is there any
way around this? Thanks

"Working on it" in what way? If you're changing the design, or editing VBA
code (not that a backend should have any code!) it will be locked; or if
you're opening it exclusively. Otherwise it should be sharable.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com

 

[pat67]

"Working on it" in what way? If you're changing the design, or editing VBA
code (not that a backend should have any code!) it will be locked; or if
you're opening it exclusively. Otherwise it should be sharable.
--

             John W. Vinson [MVP]
 Microsoft's replacements for these newsgroups:
 http://social.msdn.microsoft.com/Forums/en-US/accessdev/
 http://social.answers.microsoft.com/Forums/en-US/addbuz/
 and see alsohttp://www.utteraccess.com

I was told to split the db so that the front end would be available to
all and i could continue to work in the back end, i.e update tables
and such. i have code in the back end for improts and exports i need
to do to update the tables. the issue is if some one gets to work
before me and opens the front end, i cannot access the backend to di
the updates. then all i get is that someone is in it. no idea who
though. so what i am doing now is editing a copy of the backend and
the copying that to the original back end. i was hoping there was an
easier way.

 

[pat67]

"Working on it" in what way? If you're changing the design, or editing VBA
code (not that a backend should have any code!) it will be locked; or if
you're opening it exclusively. Otherwise it should be sharable.
--

             John W. Vinson [MVP]
 Microsoft's replacements for these newsgroups:
 http://social.msdn.microsoft.com/Forums/en-US/accessdev/
 http://social.answers.microsoft.com/Forums/en-US/addbuz/
 and see alsohttp://www.utteraccess.com

I was told to split the db so that the front end would be available to
all and i could continue to work in the back end, i.e update tables
and such. i have code in the back end for improts and exports i need
to do to update the tables. the issue is if some one gets to work
before me and opens the front end, i cannot access the backend to di
the updates. then all i get is that someone is in it. no idea who
though. so what i am doing now is editing a copy of the backend and
the copying that to the original back end. i was hoping there was an
easier way.

 

[John W. Vinson]

I was told to split the db so that the front end would be available to
all and i could continue to work in the back end, i.e update tables
and such. i have code in the back end for improts and exports i need
to do to update the tables. the issue is if some one gets to work
before me and opens the front end, i cannot access the backend to di
the updates. then all i get is that someone is in it. no idea who
though. so what i am doing now is editing a copy of the backend and
the copying that to the original back end. i was hoping there was an
easier way.

It sounds like it's the code that is the problem. I'd suggest creating your
own private frontend with the code and so on; the backend should contain ONLY
tables. You cannot of course be changing the *structure* (adding or removing
fields, changing their size or datatype) of the backend while someone is
trying to use that same table, but such changes should be very rare in a
working database application.

Unless one of you is opening the database exclusively there should not be a
lock. You might get locking if you and a user are attempting to update the
*same record* at the same time.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com

 

[David W. Fenton]

:

I was told to split the db so that the front end would be
available to all and i could continue to work in the back end, i.e
update tables and such.

Usually the advice about splitting is so that you can work on the
FRONT END without the users interfering. That is not, of course, the
only reason for splitting, but it is one reason for it.

The back end is always shared and anything that makes structural
changes (as opposed to just changing data) should not be attempted
while other users are in the database.

If you're just doing data massage and imports, perhaps you should
create a separate "front end" for that, with links to the tables in
the shared back end. That's definitely the way I'd do an import
operation like that because I wouldn't want to "pollute" the real
back end with all the churn that comes with the processing of import
data.