MS Access 2003 and Citrix

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Stephen K - 27 May 2005 13:42 GMT

I have created an Access adp project with an SQL server back end database and
I want to run it on a Citrix / Terminal Server machine. We are getting an
error on the Citrix Server about the database being open already when the
second user tries to open it. Any ideas of how to make this work would be
greatly accepted?

Is there a limitation that other Office applications can run on Citrix but
not Access?

Reply to this Message

Tony Toews - 27 May 2005 18:29 GMT

>I have created an Access adp project with an SQL server back end database and
> I want to run it on a Citrix / Terminal Server machine. We are getting an
>error on the Citrix Server about the database being open already when the
>second user tries to open it. Any ideas of how to make this work would be
>greatly accepted?

This is probably a permissions problem on the directory in which the
frontend is installed. The users must have create/delete privileges
to that directory. What is happening is that Access can't create the
.ldb file which allows multiple users to update the MDB. So Access
only allows one user at a time.

However you really want to give each user their own copy of the front
end. See the "Splitting your app into a front end and back end Tips"
page at http://www.granite.ab.ca/access/splitapp/ for more info.
Ignore the part about splitting as you've already done that with SQL
Server.

See the Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.

Tony

Signature

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

Reply to this Message

Stephen K - 28 May 2005 04:05 GMT

Thank you Tony I will refer to the Web sites however I think that it is worth
noting that when opening an adp that it would appear taht there is no ldb
created by Access. I have opened the adp application and done a search using
Windows Explorer on all hard drives for *.ldb and while it found one other
file it was not to do with the adp.

An adp does not use linked table. It has no of it won tables no links it
use the data link connection or you can establish your own

Thanks - if you have any further feedback I would be most grateful

> >I have created an Access adp project with an SQL server back end database and
> > I want to run it on a Citrix / Terminal Server machine. We are getting an
[quoted text clipped - 19 lines]
>
> Tony

Reply to this Message

tudor - 16 Jun 2005 20:42 GMT

Stephen K,

I've been through this too... you need to ensure that each Terminal
Server/Citrix user is using a separate copy of the ADP - essentially copy the
ADP file into their My Documents (or below) directory on the terminal server.
Each user will then be using a separate copy of the ADP as the ADP will be
located in their unique profile. If you point all users to the same file on
the server (i.e. c:\myadp\myadp.adp), you'll get the "file already open -
open read only copy?" problem you've been getting beacuse the other users
already have it open. ADPs don't use the mdb/ldb mechanism but are opened for
read/write access. If a second user attempts to open the same file for
read/write, they won't be able to.

The AutoFE link that you were provided (if I remember correctly) is a
utility to distribute new versions of you adp to each Citrix/TermServices
local copy - essentially by copying the newer adp file over each user's older
versions. I tried it but it was not exactly what I needed.

I ended writing a simple wrapper in VB6 that checks the database for the
name/version of the latest version of the front-end and then if necessary
copies the newer version from a network share into each user's directory, and
then launches Access and the new ADP. Works great and all my terminal server
users and lan users get the latest version on launch. A hidden form in the
ADP checks the version registered in the database every five minutes too and
warns the users that a new version exists and to relaunch to get the newer
version.

Hope this helps....

> Thank you Tony I will refer to the Web sites however I think that it is worth
> noting that when opening an adp that it would appear taht there is no ldb
[quoted text clipped - 30 lines]
> >
> > Tony

Reply to this Message

SC ChiefsFan - 26 Jun 2005 01:10 GMT

Tudor,

Do you mind sharing your VB6 code? I am working on one in VBS but am stuck
at trying to open the Access file. If it is too long to post I'll leave my
email for you.

Thanks!
Doug Miller

> Stephen K,
>
[quoted text clipped - 59 lines]
> > >
> > > Tony

Reply to this Message

tudor - 27 Jun 2005 09:01 GMT

No problem - leave me an email address and I'll send it.

> Tudor,
>
[quoted text clipped - 68 lines]
> > > >
> > > > Tony

Reply to this Message

SC ChiefsFan - 27 Jun 2005 17:29 GMT

Thanks - doug_miller at hotmail.com

> No problem - leave me an email address and I'll send it.
>
[quoted text clipped - 70 lines]
> > > > >
> > > > > Tony

Reply to this Message

Lee - 06 Jul 2005 23:44 GMT

Would having each Citrix user have a separate copy of the front end also
apply to .mde files also?

Signature

Lee
Redmond, Wasington

> Stephen K,
>
[quoted text clipped - 59 lines]
> > >
> > > Tony

Reply to this Message

Douglas J. Steele - 07 Jul 2005 00:27 GMT

Yes.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> Would having each Citrix user have a separate copy of the front end also
> apply to .mde files also?
[quoted text clipped - 83 lines]
>> > >
>> > > Tony

Reply to this Message

JD - 12 Jul 2005 15:39 GMT

>I've been through this too... you need to ensure that each Terminal
>Server/Citrix user is using a separate copy of the ADP - essentially copy the
[quoted text clipped - 6 lines]
>read/write access. If a second user attempts to open the same file for
>read/write, they won't be able to.

Hi folks:

I'm developing an .ADE database for use with Terminal Services, and I
reached the same conclusion: each user needs their own copy of the
front end to avoid permission problems. However...

I'm bound to encounter resistance from my client when I tell him he
must have a separate copy of the front end for each user. This will
mean about 50-75 copies of the front end in this case, and he will
grumble even if he has access to auto-updating tools.

Is there some formal documentation from Microsoft that makes it clear
that separate copies of the front end are required in this situation?
I'd like to have that to back up my statement and head off requests to
"keep looking" for another solution.

Thanks very much.

- Jon

Reply to this Message

Rick Brandt - 12 Jul 2005 16:18 GMT

> I'm developing an .ADE database for use with Terminal Services, and I
> reached the same conclusion: each user needs their own copy of the
[quoted text clipped - 9 lines]
> I'd like to have that to back up my statement and head off requests to
> "keep looking" for another solution.

Unfortunately, MS' position is that splitting is only a performance
enhancement. They don't "officially" say that sharing a monolithic file
will lead to corruption and other problems when just about anyone who has
ever used Access seriously recognizes this fact.

Signature

I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Reply to this Message