ldb problem

  • Thread starter Thread starter JohnE
  • Start date Start date
J

JohnE

I have a db (fe/be)out on the Citrix server. I works fine
but yesterday I put 2 updates out there and didn't have a
problem. When I went last night and put a third update
out there I got the notice that there are more then one
trying to change the same data. I ran into this when I
would try and compact and repair. No one else is on. I
found that I cannot delete the ldb or the main front end
file. The server person was able to show that when I was
not on, the ldb was not showing. He could delete the main
front end and replace it but when I would try to my thing,
I would still get the message about the jet database and
more then one trying to change the same data.
Has anyone else come across this problem and if so what
was done to correct? Otherwise, does anyone have any
suggestions?
*** John
 
What does the server show for people who have files open?

I am not in front of a server right now...but in there some where is some
utilities that show the list of open files and by who/what users. It seems
to me that perhaps someone is not logging off their terminal session, but
simply disconnecting the session, and when they re-connect/re-logon their
current status (with the files open) is restored. This is likely what is
happening in your case.

I would NOT start deleting ldb locking files for data files. This is
especially the case for the back end file. For the front end ldb
file?...sure...go ahead and kill it. However, if you are taking about the
back end ldb file....then don't do it.


Further, as for the front end file. you are NOT to share the same front end.
Each terminal user (citrix and terminal services are the same thing). In
other words, just like standard network setup, each user gets their own
copy of the front end. When using TS/Citrix, again each users gets THEIR OWN
COPY OF THE FRONT END! You do not want to allow multiple users in the same
front end. Once again:

Each user gets their own copy of the front end.

If there is ANY thing un-clear in the above single sentence, please feel
free to ask more questions.
 
Look up a technical article in the Microsoft knowledge
base on opportunistic locking. There is a security patch
that you may want your server people to explore putting
on your server.
This solved the issue for us.
 
JohnE said:
I have a db (fe/be)out on the Citrix server. I works fine
but yesterday I put 2 updates out there and didn't have a
problem. When I went last night and put a third update
out there I got the notice that there are more then one
trying to change the same data.

To add to Albert's comments I specifically created the Auto FE Updater
utility so that I could make changes to the FE MDE as often as I
wanted and be quite confident that the next time someone went to run
the app that it would pull in the latest version. For more info on
the errors or the Auto FE Updater utility see the free Auto FE Updater
utility at http://www.granite.ab.ca/access/autofe.htm at my website to
keep the FE on each PC up to date.

In a Terminal Server or Citrix environment the Auto FE Updater now
supports creating a directory named after the user on a server. Given
a choice put the FE on the Citrix server to reduce network traffic and
to avoid having to load objects over the network which can be somewhat
sluggish.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
chrissie said:
Look up a technical article in the Microsoft knowledge
base on opportunistic locking.

Also see the Corruptions FAQ at my website.
There is a security patch
that you may want your server people to explore putting
on your server.
This solved the issue for us.

I'm just curious here. What problems were you having? I ask because
JohnE's problem doesn't sound like an corruptions problem to.
Although it certainly could be.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top