User cannot create query in Access 97 (XP Professional)

Topic

New Reply

We have PC’s connected to a domain network using Windows XP Pro. When a user who has power user status on his PC tries to create a query in access 97 or import an Excel file he basically gets a message denying him access to do this. An user with administrator access can do this with no problems. Now, we do not want to give users admin access to their PC’s. Obviously this is a Microsoft security “feature” but is there perhaps a registry setting that can give him access to do these things or do we have to bite the bullet and set him up as a local admin.

Reply | Quote

Replies

Is the user trying to create a query AND import a spreadsheet into Access? If so, this is probably not XP related, but rather an Access security issue. You will have to set up security within Access to enable or disable privileges.

Reply | Quote

The user himself created the database when he was using Windows NT. Now he has a new PC running Windows XP Pro and is having problems with the database since switching. The database is located on a network drive he has full access to. If he uses his old NT PC he can still use the database with no problems.

Reply | Quote

Is the user trying to create a query AND import a spreadsheet into Access? If so, this is probably not XP related, but rather an Access security issue. You will have to set up security within Access to enable or disable privileges.

Reply | Quote

Does the EU have ownership rights to the Database? If not, can you give them to him? As he already far enough inside the DB to create queries, it sounds like it is not an Access security issue.

From what you say, I take it that he is trying to carry out the development work on his own hard drive. Is that really so?

Reply | Quote

The user himself created the database when he was using Windows NT. Now he has a new PC running Windows XP Pro and is having problems with the database since switching. The database is located on a network drive he has full access to. If he uses his old NT PC he can still use the database with no problems.

Reply | Quote

Is he using the same login on both PCs?

Joe

--Joe

Reply | Quote

Yes, that hasn’t changed. We had another user who swapped form WinNT to W2K who had a similar problem. Changing him to power user worked OK but not it seems with Windows XP Pro.

Reply | Quote

Has the End User tried creating a new Database on his Windows XP machine and then importing all the objects from the old Database? HTH

Reply | Quote

No have not tried this. Do you think that security is set up differently if the user creates the dataabse? This will not help for other databases he has to access. (of which there are many) It would be too much work to create them all again on his PC.

Reply | Quote

I have not tried recreating databases in bulk, but, in principle, it should only take a few minutes per database. You say ltlle about your set-up, but, in a number of cases, it would not necessarily be likely that a developer would have to go back and create new queries in most of them. Are there no plans to upgrade your Access licences from 97 to 2003? It may be the case that this is an Access 97 only issue. If there is no Office upgrade planned and the exisitng databases are “high maintenance”, you seem to have little choice but to grant Admin permissions on his local machine. HTH

Reply | Quote

For this user I would not like to grant him this amount of access.

Reply | Quote

For this user I would not like to grant him this amount of access As you may have inferred from my previous comment, my instinct is that this EU is “trying it on”. Unfortunately, there is the very occasional case where an issue is artificially created to achieve elevated privileges.

Reply | Quote

For this user I would not like to grant him this amount of access As you may have inferred from my previous comment, my instinct is that this EU is “trying it on”. Unfortunately, there is the very occasional case where an issue is artificially created to achieve elevated privileges.

Reply | Quote

For this user I would not like to grant him this amount of access.

Reply | Quote

I have not tried recreating databases in bulk, but, in principle, it should only take a few minutes per database. You say ltlle about your set-up, but, in a number of cases, it would not necessarily be likely that a developer would have to go back and create new queries in most of them. Are there no plans to upgrade your Access licences from 97 to 2003? It may be the case that this is an Access 97 only issue. If there is no Office upgrade planned and the exisitng databases are “high maintenance”, you seem to have little choice but to grant Admin permissions on his local machine. HTH

Reply | Quote

No have not tried this. Do you think that security is set up differently if the user creates the dataabse? This will not help for other databases he has to access. (of which there are many) It would be too much work to create them all again on his PC.

Reply | Quote

Has the End User tried creating a new Database on his Windows XP machine and then importing all the objects from the old Database? HTH

Reply | Quote

Is he logging into the domain or to the local PC?

Joe

--Joe

Reply | Quote

He logs on to the domain.

Reply | Quote

Was Office installed by a local administrator user? Is it fully patched? Try this google search: access 97 security group:microsoft.public.windowsxp.*
It should give you lots to investigate.

Joe

--Joe

Reply | Quote

Office was installed by an administrator. It actually has Office 2002 and Access 97 installed. Access 97 is SR2a.

Reply | Quote

I had a similar problem when I was still working at a company that had a network. My new computer had Windows 2000 on it and the one that was replaced had Windows 95. After many hours and a lot of failures it turned out that the passwords for my local drives and for the network drives were not being totally recognized by each other. Even though I always kept the passwords the same so I didn’t have so many to remember, it was a password synchronization problem. I don’t know what the network administrator eventually did to correct it but after about 2 months he did get it straightened out. In the meantime we moved all my database programs to my local drives and when someone else need them I gave them temporary access to a folder on my PC.

Reply | Quote

I had a similar problem when I was still working at a company that had a network. My new computer had Windows 2000 on it and the one that was replaced had Windows 95. After many hours and a lot of failures it turned out that the passwords for my local drives and for the network drives were not being totally recognized by each other. Even though I always kept the passwords the same so I didn’t have so many to remember, it was a password synchronization problem. I don’t know what the network administrator eventually did to correct it but after about 2 months he did get it straightened out. In the meantime we moved all my database programs to my local drives and when someone else need them I gave them temporary access to a folder on my PC.

Reply | Quote

Remember must be a LOCAL admin not a domain admin otherwise non-admin users will have problems. Why have Office XP and Access 97? Why not all XP? I doubt it is a good idea to have two versions of Office that different in age installed on the same PC. Much has changed in Office and the OS since Office 97 was released. All of the Office suite is much more integrated. There is so much more sharing of components that could be part of the problem.

Joe

--Joe

Reply | Quote

Most of the staff have Office 97 and only a few of the PC’s have Office XP or 2000. All the databases are shared so must be in the lost common denominator format which is Access 97. Sharing of components is not the problem as an adminsitrator on the same PC has no problems.

Reply | Quote

Did you look at the results from the google search in post 359712 ?

Joe

--Joe

Reply | Quote

Did you look at the results from the google search in post 359712 ?

Joe

--Joe

Reply | Quote

Most of the staff have Office 97 and only a few of the PC’s have Office XP or 2000. All the databases are shared so must be in the lost common denominator format which is Access 97. Sharing of components is not the problem as an adminsitrator on the same PC has no problems.

Reply | Quote

Remember must be a LOCAL admin not a domain admin otherwise non-admin users will have problems. Why have Office XP and Access 97? Why not all XP? I doubt it is a good idea to have two versions of Office that different in age installed on the same PC. Much has changed in Office and the OS since Office 97 was released. All of the Office suite is much more integrated. There is so much more sharing of components that could be part of the problem.

Joe

--Joe

Reply | Quote

Office was installed by an administrator. It actually has Office 2002 and Access 97 installed. Access 97 is SR2a.

Reply | Quote

Was Office installed by a local administrator user? Is it fully patched? Try this google search: access 97 security group:microsoft.public.windowsxp.*
It should give you lots to investigate.

Joe

--Joe

Reply | Quote

He logs on to the domain.

Reply | Quote

The domain.

Reply | Quote

The domain.

Reply | Quote

Is he logging into the domain or to the local PC?

Joe

--Joe

Reply | Quote

Yes, that hasn’t changed. We had another user who swapped form WinNT to W2K who had a similar problem. Changing him to power user worked OK but not it seems with Windows XP Pro.

Reply | Quote

Yes its the same.

Reply | Quote

Yes its the same.

Reply | Quote

Is he using the same login on both PCs?

Joe

--Joe

Reply | Quote

The user himself created the database when he was using Windows NT. Now he has a new PC running Windows XP Pro and is having problems with the database since switching. The database is located on a network drive he has full access to. If he uses his old NT PC he can still use the database with no problems.

Reply | Quote

Another possibility to check is to make sure that he has full priviledges to the folder in which the database resides – Access requires that in order to allow the user to modify the database, compact it and so forth.

Reply | Quote

Another possibility to check is to make sure that he has full priviledges to the folder in which the database resides – Access requires that in order to allow the user to modify the database, compact it and so forth.

Reply | Quote