Access 2000 runtime installations on XP - conflicts

[JRB]

I'll try to make this brief. We have a program we've developed in Access
2000 and we distribute the runtime version of the software to users across
the country. We have a user who is having the following installation issue:

He logs on to XP by selecting his user profile from the welcome screen. He
recently installed our software, and, after installing, it would not let him
open it. Their network administrator logged on as an admin and it opened up
without a problem. What could the issue be in this scenario?

They also have Office / Access 2003 installed and use it for some other
functions. Could this be causing any problems...? I wouldn't think that it
is the culprit, just because when logged on as admin everything works just
fine.

I'm venturing to guess that it has something to do with his network
permissions or possibly the way his user profile is set up, but don't really
know where to start. I've not spoken with him personally, so I don't know
what kind of error messages he's getting - just know that it won't work when
he logs on but under admin it works fine.

Any help would be greatly appreciated!!!!!!!

 

['69 Camaro]

Hi.

First, you need to apologize to your customer and explain that you gave him
the wrong version of the software. Since his computer already had a
compatible retail version of Access installed, he only needed the database
file, not the Access Runtime. Then explain to him that you are truly sorry
that your software overwrote some of his MS Office 2003 files and he'll have
to take the time to either replace these files from backup or reinstall MS
Office 2003, reconfigure it again, and then reinstall MS Office 2003 SP-1,
because your installation program doesn't bother checking for existing
versions of Access. Then you need to fix your installation program so that
this never happens again.

after installing, it would not let him
open it. Their network administrator logged on as an admin and it opened up
without a problem. What could the issue be in this scenario?

The user's Windows account needs "Full Control" Windows security permissions
on the directory where the database file is located, on the directory where
the default SYSTEM.MDW file is located (try C:\Documents and
Settings\UserName\Application Data\Microsoft\Access), and for Access 2000
only, on the user's TEMP directory. The user's Windows account also needs
appropriate permissions in the Windows Registry to run Access.

And yes, the customer should probably uninstall the Access 2000 Runtime to
recover disk space on his computer. If your database application has custom
commandbars that the retail version's built-in commandbars might interfere
with, then the application can be opened with the /Runtime command-line
switch in a Windows shortcut. The syntax is (watch out for word wrap -- it
should be all one line):

"<FullPathToAccess2003>\MSAccess.EXE" "<FullPathToDB\MyDB.MDB" /Runtime

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)