Hi,

I have a weird problem...

We have a program that is sometimes used on a network.  On a windows 2000 network we have problems with users being able to insert or update an access database from our program.  They can select from it.

This applies even to people with domain admin/admin rights.  The network in question is locked down pretty tight and it doesnt happen to workstations not on the domain, so I am thinking its a permissions problem.

The IT people dont care and its not their problem as far as they see it.

I wonder if I can make my program login to the system account when the user logs into the program. Is there a way to do this?

Thanks!

It's not a answer to you're question, but some possible tips/ideas:

1) you can always schedule a program to run in the system accound (AT command), but then you don't have ANY network access.
2a) offhand I don't think a system account running a program has any network rights, so if it requires the network it won't work.
2b) I don't think part of the program running in the system will work any differently.

as far as being able to view, but not change the database...
3) make sure the database is setup on a shared folder that allows (all users needed) to make changes to the folder and files. If they can't, (can't remember if it's write, full or what for the rights) NT will block the updates, reguardless of how the program's designed (making it a IT problem).
4) make sure the connections allow updates (dynamic, lock optimistic) from the program.
5) if you have security setup in the database itself, make sure it allows updates.

offhand given what you've said it seems like point 3 may apply more than the others.