"Access can't start because there is no license for it on this machine"WinXP + Office 2004

L

Luke Dalessandro

Hi all,

Here's the situation... I developed an access database for a client with
the following configuration:

Back End: Windows 2k Server, Access 2000 .mdb
Workgroup File: Windows 2k Server, Access 2000 .mdw
Front End: Windows 8/ME/2000/XP, Access 2000 .mde

Without telling me, they upgraded a couple of their Windows XP Office
2000 installations to Office 2004.

The systems that were upgraded are tossing the "Access can't start
because there is no license for it on this machine" on startup.

This seems to be covered in
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q141373 but no
mention is made of Office 2004 or Windows XP.

The systems having trouble with my .mdw protected database have no
trouble with FE/BE setups that aren't .mdw protected. I gave them the
pure .mdb front end to test, and they had the same problems.

The client doesn't really have any IT staff so to speak of, so I have to
talk someone through the knowledge base solution, and if it makes Office
(or the computer) unusable I have big problems.

My question is basically, "should I be worried about my versions not
being listed in the kb article, and the .mdw specific problem?" Can I
expect the kb solution to work? I don't want to expose the system to
danger if it's not going to help matters at all.

Thanks in advance,
Luke
 
C

cleabn21

Luke Dalessandro said:
Hi all,

Here's the situation... I developed an access database for a client with
the following configuration:

Back End: Windows 2k Server, Access 2000 .mdb
Workgroup File: Windows 2k Server, Access 2000 .mdw
Front End: Windows 8/ME/2000/XP, Access 2000 .mde

Without telling me, they upgraded a couple of their Windows XP Office 2000
installations to Office 2004.

The systems that were upgraded are tossing the "Access can't start because
there is no license for it on this machine" on startup.

This seems to be covered in
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q141373 but no
mention is made of Office 2004 or Windows XP.

The systems having trouble with my .mdw protected database have no trouble
with FE/BE setups that aren't .mdw protected. I gave them the pure .mdb
front end to test, and they had the same problems.

The client doesn't really have any IT staff so to speak of, so I have to
talk someone through the knowledge base solution, and if it makes Office
(or the computer) unusable I have big problems.

My question is basically, "should I be worried about my versions not being
listed in the kb article, and the .mdw specific problem?" Can I expect the
kb solution to work? I don't want to expose the system to danger if it's
not going to help matters at all.

Thanks in advance,
Luke
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

WinXP 2002: Microsoft Access can't start because there is no license for it on this machine 6
exclusive access to the database error. Office 2003 upgrade. 1
Access cannot start because there is no license w/office 2003 & XP 4
Access can't run because there is no license?? 3
"Microsoft Access Can't Start because there is no License on this. 1
How do I overcome Access can't start because no license? 2
Access 2000 Database becomes corrupted when changed on XP Machine 5
Access 2003 RT on Server 2008 R2 64bit 0

Top