Question : How to install MS Access 2000 runtime application on Terminal Server?

I have installed many MS Access runtime applications on various pc's and operating systems, but the latest customer request has me confused.  We use Wise InstallBuilder8.14 along with SageKey scripts to install our front-end/back-end Access 2000 runtime application (a maintenance management database).  The process has been relatively easy with only a few minor problems.  However, we have a new customer who has a quad 64-bit processor running MS Windows Server 2008 with Terminal Server (in 64 bit mode).  We plan to use one back-end Access mdb database, and an Access mde front-end program db in each user's logon folder.  We expect about 10 remote connections over the internet  What is the correct process for this type of installation?  I don't quite understand how to use the mst transform.  Please help.  Thanks !!

Answer : How to install MS Access 2000 runtime application on Terminal Server?

I'll take a stab at this.  I use an MS Access MDE with a SQL Backend... but originally I had Access as the backend.  It should work similarly.  Though I do my client install manually without an install wizard due to the nature of our small business.  However... I do have 5-10 users that use Terminal Server to run the MDE client.

After the user folder has been created:

C:\Documents and Settings\{account}

I create a folder for my application.  This folder contains two files... a .cmd and .mde (the CMD does 3 things)
1) map a drive letter to the server\folder that is the location of the application
2) copy a fresh version of the .mde from the mapped drive
3) launch the mde

The  runtime.mde has the linked tables to the backend database defined based on the mapped drive.

I didn't understand the last sentence of your post... "... how to use the mst transform" - so my suggestion might miss the mark.  However... I've had much success running my Access .mde from client computers and Terminal Services using the .cmd attached.  (and I just put a shortcut in their Users / Desktop that points to the .cmd )

1: 2: 3: 4: 5: 6:

NET USE Q: /D NET USE Q: \\{server}\{share} copy Q:\client\runtime.mde start runtime.mde cls exit

Open in New Window Select All