JIM.H. said:
We bought Microsoft Access 2003 Developer Extensions to be
able to get runtime running in our terminal server to
avoid many Access 2002 licenses. My questions;
1. After installation, how should I launch my MBD?
Each user will need to run the app install to create Program Files
menu items. Or you should be able to use the Auto FE Updater to
create shortcuts on the users desktops.
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.
2. Can I keep my Access 2002 installed in the terminal
server (I have one license for this) for only my usage and
get users run MDB through runtime? Does this violate
licensing issue?
You need to purchase MS Office 2003 before you can use the A2003
Developer Extensions. It won't run from A2002. Thus you might as
well use that copy for your use on either the Terminal Server or your
own PC. Also you can use it to create an MDE thus locking your
users out of updating forms or reports.
Also see Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm
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