Problem: Network programming, OpenWorkspace?

[mpltkvx]

Hello,

This is a question regarding MS-Access programming.

1. Network environment:
I got a room with 50 people answering the phone and logging the topics
of the incoming calls. Each has a PC, and the PC's are connected by
LAN to a Windows 2000 server PC.


2. Software Environment:
I built a small MS-Access database program which has the topics as
YES/NO fields. There are also a date/time field and a COMPUTERNAME
field for each logged call. Currently all of the users are opening this
program, which resides on a shared-location on the server, and feeding
directly to the server.

3. My wishlist:
I want to make a program which resides locally in a shared location on
each of the user's computers, and feeds to a database local to the
user's computer. At some instance, I, the network-administrator, will
have a program which logs into each of the shared locations of the
user's computers, opens the current users' database and harvests
their data to my own database table by way of a SQL INSERT INTO
command, or differently.

4. My problem:
These shared locations, of the users, are protected by a
login/password. I must keep the login/password on. I need a
programmatic way to log into the current shared location. How do I do
it? OpenWorkspace only handles the password of the user in ACCESS
itself, not in the network. Do I have to use DDE/SendKeys to handle the
dialog being opened when I log in manually?

Thanks in advance,
Max.

 

[Douglas J. Steele]

Why not do the standard split: have a front-end (containing the queries,
forms, reports, macros and modules) and a back-end (containing the tables
and relationships)? Each user gets his/her own copy of the front-end, on
his/her hard drive, while the back-end resides on the server, with each user
updating it. With 50 people (and depending on the call volume), you might
consider using SQL Server for the back-end.

 

[Tony Toews]

With 50 people (and depending on the call volume), you might
consider using SQL Server for the back-end.

Actually I'd definitely go with SQL Server. One corruption and
you've lost the days calls. Kinda scary if there is no paper
backup.

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