If your application runs on the TS machine and the DB is on another machine,
the you could use a System DSN [that's DSN not DNS
] to access the DB.
The Application would have to be written to use the DSN. There are also way
with in Programming to create a DSN-less connection (which is better than a
DSN), but that gets into the guts of writtng program code that I can't help
with.
Using either of those methods can allow multiple Applications from multiple
locations to access the same DB at the same time.
But this isn't something that you can just "wing it",..the Application has
to be written from the start to work that way and the Application must be
properly installed on the TS through the Add/Remove Programs so that the
Terminal Service can monitor and process the installation properly. Also
sometimes Applications just will not work properly in the multi-user
environment of Terminal Services.
Now if this is a regular simple MS Access Application then it needs to have
the MDB file
"split" into the two files for the Front End and the Back End. The Back End
file contains the Data and is centrally stored,..the Front End file acts as
the Application and there can be multiple copies of them (I think). I do
not know how well something like that will function in the multi-user
environment of Terminal Services. See people who are experts with MS Access
for these details,...I am not one of them
.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"patti" wrote in message
news:A5E4F5B1-E237-4461-8FE0-372C7B7DD6E8@microsoft.com...
> Philip-
>
> Thank you very much for the clear answer.
> I figured since i could open db's on the other db a batch file would be no
> problem, but needed confirmation. Do you have any suggestions on a basic
> primer for wts?
>
> "Phillip Windell" wrote:
>
>> Batch files run whatever you run from the machine (the processor, the
>> RAM)
>> the batch file was executed on (the WTS in this case). Where the
>> executable
>> that the batch file called resides is totally irrelevant. So the VBA
>> Macros
>> are coppied accross the network into memory on the WTS machine and are
>> executed within RAM on the WTS macine. The fact that the VBA files were
>> stored elsewhere is not relevant, they are not executed at the location
>> they
>> are stored at.
>>
>> --
>> Phillip Windell
>> www.wandtv.com
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>>
>> "patti" wrote in message
>> news:34393D58-4CF4-4B50-8A61-D76C4EEE5237@microsoft.com...
>> > MS Access is installed on windows terminal server.
>> > My access db is on another (non-wts) server.
>> > Can i put a batch file on the wts to run vba macros from the non-wts
>> > db?
>> > (i want to use wts scheduler to launch batch)
>> >
>> > thanks.
>> >
>> > patti
>>
>>
>>