run mdb in a terminal server

[JIM.H.]

Hello,
I am wondering how do people use an Access 2002
application in terminal servers. Users need to run mdb
file, we have 20 users if they all run the same mdb at the
same time will it cause any problem?
Thanks,
Jim.

 

[Steve Schapel]

Jim,

Yes, it will cause problems if all the users run the same mdb. You
should have a separate copy of the mdb for each user, within each user's
own folder or user profile on the server.

 

[JIMH.]

Thanks Steve,
What might be the problem be? Is there any other way? The
file is almost 500MB and it may not be easy to create a
separate one for 20 users.
Thanks,
Jim.

 

[Steve Schapel]

Jim,

I am sorry, I think I misinterpreted your original question. I assumed
you have the database split into 2 files, the backend with the core data
tables, and the frontend with the forms, reports, queries, etc, with
links to the backend tables. If this is not the configuration you are
using, then this is what I would recommend. Obviously there can only be
one copy of the backend data. And then it is the frontend that each
user needs their own copy of. When you refer to 500MB I assume this is
not the size of a frontend application file.

 

[Tony Toews]

I am wondering how do people use an Access 2002
application in terminal servers. Users need to run mdb
file, we have 20 users if they all run the same mdb at the
same time will it cause any problem?

Access works fine in a Terminal Server environment. Although some
versions require a special transform file.

See My random thoughts on Microsoft Access, Terminal Server and/or
Citrix http://www.granite.ab.ca/access/terminalserver.htm for my stuff
and links to MS KB articles.

You must also split the MDB. See the first few paragraphs at the
above page.

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

 

[JIM.H.]

Steve,
I am using some of the tables at the back end access db
and some in the front end application. The tables that I
am keeping in front end is actually created at runtime by
retrieving some data from another database. Even if I
delete all the records in these local tables the size of
mdb is still 300MB.

Also I have some reports that have logo in it. Logo is a
jpg and 200KB, do you think that this is the reason for
that. I have 19 reports that have this logo. I use image
tool to import logo file, does access 2000 read it from
the file or import it into application?
Thanks,
Jim.

 

[Steve Schapel]

Jim,

It is probably appropriate for the temporary tables to be in the
frontend, although some people would feel it is better to create a
temporary local database for these tables at runtime. HAve you
compacted the friontend mdb lately?

But yes, the logo image files are likely contributing a lot to the
overall size of the file. There are a number of ways to reduce this,
one of which is to link to the .jpg rather than embedding in the report,
but even then I think it bloats the database. One approach you could
look at is leaving the logo blank on the report design, and using code
on the On Format event of the reports to set the Picture property of the
image control to the path to the .jpg file.

 

[Tony Toews]

I am using some of the tables at the back end access db
and some in the front end application. The tables that I
am keeping in front end is actually created at runtime by
retrieving some data from another database. Even if I
delete all the records in these local tables the size of
mdb is still 300MB.

To add to Steve's reply:

See the TempTables.MDB page at my website which illustrates how to use
a temporary MDB in your app.
http://www.granite.ab.ca/access/temptables.htm

Also I have some reports that have logo in it. Logo is a
jpg and 200KB, do you think that this is the reason for
that. I have 19 reports that have this logo. I use image
tool to import logo file, does access 2000 read it from
the file or import it into application?

Steve's right on this one.

At the very least create a report which has the logo on it and nothing
else. Then use that as a subreport in all the other reports. Then,
later, you can add a few lines of code to pull it in as a file. Do
the same for logo's on forms.

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