If I deploy an application to a terminal server (Windows 2008 64 bit) it
runs OK for me but if someone else opens it, the objects seem to
disappear out of the navigation pane and errors occur like "cannot find
form xxx" even though that form should exist.

If that user compacts the database then it runs fine, until they log out
and log back in again the same thing occurs. Compacting the database
fixes it for that session only.

If I open the database after the other person has compacted it then the
same error occurs until I compact it myself.

No-one is opening it simultaneously.

If I deploy to a machine running Windows XP it is fine, even with
different people logging in on RDP.

The Windows group Everyone has full control to the folder where the ACCDB
file is, happens with ACCDE files as well.

--
Travis Crow

Travis Crow <noreply (AT) invalid (DOT) org> wrote in
news:4d751c1d$0$12173$fa0fcedb (AT) news (DOT) zen.co.uk:

Office 2010 requires the Enterprise version to run on Windows
Terminal Server, right?

It sounds like you're sharing a database, and you shouldn't do that
(except the back end) on Terminal Server any more than you should do
it on an individual workstation. Each user needs their own copy of
the front end (your app is split, right?).

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On Mon, 07 Mar 2011 19:56:07 +0000, David-W-Fenton wrote:

It's "Pro" but the install key is one for terminal server, it refuses to
install with the normal cd key.

It is split, actually SQL Server back-end, only one user was on it at any
one time. See above:

--
Travis Crow

Travis Crow <noreply (AT) invalid (DOT) org> wrote in
news:4d76593b$0$2508$db0fefd9 (AT) news (DOT) zen.co.uk:

....that is, you have to have an Enterprise key to install it.

No one is opening WHAT simultaneously? Obviously, not the back end.
But are you trying to share a front end? Saying it's split is only
half the battle -- you also have to make sure mutliple users aren't
opening the front end at the same time.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On Wed, 09 Mar 2011 18:36:19 +0000, David-W-Fenton wrote:

No-one is opening the front-end simultaneously

--
Travis Crow

Travis Crow <noreply (AT) invalid (DOT) org> wrote in
news:4d78b8c7$0$12158$fa0fcedb (AT) news (DOT) zen.co.uk:

Then I don't really understand what you meant when you wrote:

Why don't you give explicitly steps for what is being done that's
causing the problem?

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On Fri, 11 Mar 2011 23:50:36 +0000, David-W-Fenton wrote:

As above, user A deploys app on terminal server, runs it, it's OK
User A logs out
User B logs in, runs app, problem occurs
User B Compacts database, is OK
User B can close database and re-open it no problem but if user B logs
out then logs back in again, the same problem occurs.

I did manage to reproduce the problem on a workstation, but only once,
again, compacting the database fixed it. It's as though there's some sort
of corruption occurring.

It's as though the database is possibly not getting closed when the user
logs out of the terminal server, perhaps Access is getting stuck in
memory and keeping it open but this doesn't appear to be the case as I
have monitored for instances of msaccess.exe in task manager and it is
exiting whenever a user exits the app. Unless there's a rouge DLL sitting
around in memory that's got the database open but then I wouldn't be able
to compact it.

--
Travis Crow

Travis Crow <noreply (AT) invalid (DOT) org> wrote in
news:4d920546$0$12173$fa0fcedb (AT) news (DOT) zen.co.uk:

Is it split? Does each user have their own copy of the front end? If
not, that's a likely cause of issues (though with only one user at a
time, it should work unsplit, or with a "shared" front end).

Well, that shouldn't be an issue if the app is properly deployed,
i.e., split, and with each user having an individual copy of the
front end.

I don't know, but the first thing to clarify is if your app is
properly deployed or not (i.e., split with an idividual copy of the
front end for each user).

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

On Mar 7, 6:55*pm, Travis Crow <nore... (AT) invalid (DOT) org> wrote:
Travis, I have experienced a similar problem, which I highlighted in
another thread:
http://groups.google.com/group/comp....79efb80f8f0a7#

When I relink the front-end tables to the back-end, whether by code or
via the ribbon, the navigation pane goes blank and I get a similar
error message to you.

If however I compact and repair everything before attempting to open a
form it is OK.

This is just another oddity that I have come across in upgrading from
A2000 to A2010

Jim