[AccessD] Running Access 2002 runtime on an Windows XP machine

Charlotte Foust cfoust at infostatsystems.com
Thu Dec 9 18:22:53 CST 2004


If there is no Access security, then it has to be a Windows permissions
issue, which is outside the scope of Access.  You have checked to be
sure the mdb file isn't read only, right?

Charlotte Foust


-----Original Message-----
From: Spam [mailto:JohnSkolits at corporatedatadesign.com] 
Sent: Thursday, December 09, 2004 2:41 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Running Access 2002 runtime on an Windows XP
machine 


There is no access security and the ldb file will be created in the same
folder as the app. And they should have all rights to that folder. So
I'm not sure who or what is preventing the ability to add or delete
data. Note that even "super user" doesn't work.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Thursday, December 09, 2004 4:48 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Running Access 2002 runtime on an Windows XP
machine 


Our clients run like this all the time.  We assume that our users are
NOT the OS administrators.  Are you using Access security?  In order to
delete records, they have to be able to log in and create the LDB file
if it doesn't already exist.  If they have no permissions to
create/write/delete that file, they won't be able to delete any records.

Charlotte Foust


-----Original Message-----
From: Spam [mailto:JohnSkolits at corporatedatadesign.com] 
Sent: Thursday, December 09, 2004 1:15 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Running Access 2002 runtime on an Windows XP machine 


Sorry if this was posted twice.

 

Anyone have a problem running a 'runtime' version of Access on a machine
in which the user is not the "OS "administrator?  I have tried "super
user" but the user can't delete any records. Says no permissions.

This is not the user logging into Access that seems to be the issue. It
seems to be the user logging onto the PCs operating system when they
start the PC. A user with operating system administrative rights has no
problem. 

Also, if I log on to the OS as the user with limited rights and run the
app as an administrator (can do that by right-clicking on the apps, icon
and selecting :"Run As") it the app runs with no problems..

Any ideas? Any way of launching an app and specifying the administrator
as the user. Maybe a command line argument?

Thanks,

John

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list