Re: Help needed w/Runtime, XP, and "Can't be started…" error
From: John Moore (masprog_at_attglobal.net.invalid)
Date: 07/12/04
- Previous message: Jean: "Access 2000 Runtime Setup Switches"
- In reply to: Tony Toews: "Re: Help needed w/Runtime, XP, and "Can't be started…" error"
- Next in thread: Tony Toews: "Re: Help needed w/Runtime, XP, and "Can't be started…" error"
- Reply: Tony Toews: "Re: Help needed w/Runtime, XP, and "Can't be started…" error"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Jul 2021 18:32:14 GMT
Tony,
Thanks for all your help. We were able to solve this problem in one of
our installations by giving the user full Admin rights. That is not
something a lot of installations want to do so we are trying to figure
out what other options (i.e., which policies and permissions) can be
changed so that the user can operate properly without the full Admin
profile.
When we find out, I will post it back to the newsgroups.
TC
Tony Toews <ttoews@telusplanet.net> wrote:
>Tony Toews <ttoews@telusplanet.net> wrote:
>
>>No idea on policies but I'm doing a bit of mucking with permissions.
>>There is a KB article on A97 and NTFS permissions. Security
>>Requirements When Using NTFS Partition
>>http://support.microsoft.com/?kbid=169387 but I don't know how
>>applicable this is to a Sagekey runtime.
>
>This KB article is applicable only to NT 4.0.
>
>Tony
- Previous message: Jean: "Access 2000 Runtime Setup Switches"
- In reply to: Tony Toews: "Re: Help needed w/Runtime, XP, and "Can't be started…" error"
- Next in thread: Tony Toews: "Re: Help needed w/Runtime, XP, and "Can't be started…" error"
- Reply: Tony Toews: "Re: Help needed w/Runtime, XP, and "Can't be started…" error"
- Messages sorted by: [ date ] [ thread ]