D
Dawna
We have just converted from Access 97 to Accesss 2002.
All users will only have Access runtime installed.
We have a number of databases. Previously every time a
user wanted into a database they would have to log into
that specific database. User securty is turned on. A bit
time consuming for those who use multiple databases all
day.
I wrote a dispatch program that once the user logged into
it, the concept was that they wouldn't have to log in
again. In the command line for the initial dispatch
program I have the \wrkgrp designated.
The concept is that the user clicks a button and another
database is opened - seamlessly. To open the database I'm
using a macro with the "SelectObject" and SendKeys
actions. I'm more comfortable using VBA but couldn't find
the suitable statement. This works for me (Admin rights)
with a full blown development install but I'm having
problems getting it to work for lesser users with only
RunTime installed. It appears like the workgroup
information is not passed along when the user opens the
second database.
Any suggestions on a (better?) way to do this would be
much appreciated.
Dawna
All users will only have Access runtime installed.
We have a number of databases. Previously every time a
user wanted into a database they would have to log into
that specific database. User securty is turned on. A bit
time consuming for those who use multiple databases all
day.
I wrote a dispatch program that once the user logged into
it, the concept was that they wouldn't have to log in
again. In the command line for the initial dispatch
program I have the \wrkgrp designated.
The concept is that the user clicks a button and another
database is opened - seamlessly. To open the database I'm
using a macro with the "SelectObject" and SendKeys
actions. I'm more comfortable using VBA but couldn't find
the suitable statement. This works for me (Admin rights)
with a full blown development install but I'm having
problems getting it to work for lesser users with only
RunTime installed. It appears like the workgroup
information is not passed along when the user opens the
second database.
Any suggestions on a (better?) way to do this would be
much appreciated.
Dawna