G
Guest
I have an application that I developed in Access2003. I recently made a lot
of changes to it and repackaged it for installation. I have two Windows-XP
Prof. machines that had the original version of my software up and running
on them. When I went to copy the new *.mdb file to these computers, there
were a lot of "..... Can't find project or Library..." errors. I
uninstalled the old version of my application and the Access2003 runtime
from these two machines. I then re-installed the new version and there are
still a lot of those errors.
I went back to the programming machine and went through all of the
references to see if any were missing... there were none missing. I then
programmed a few lines to show me the references on the runtime machines and
there were still no missing referrences.
I then installed the new version onto a completely virgin XP machine and
there were no errors. The problem is that I have to be able to install this
new version on machines that have the older version of my application but I
can't duplicate the error in the programming environment and the error
doesn't occur on a virgin machine. Both versions of my application were
developed with Access2003 using the 2003 runtime to distribute.
Why is this happening and what can I do to fix it? Its driving me nuts!
--TonyD--
(This same message was also posted in ...developers.toolkits and
....devtoolkits with no responses for 2 days... that's why I'm also posting it
here.)
of changes to it and repackaged it for installation. I have two Windows-XP
Prof. machines that had the original version of my software up and running
on them. When I went to copy the new *.mdb file to these computers, there
were a lot of "..... Can't find project or Library..." errors. I
uninstalled the old version of my application and the Access2003 runtime
from these two machines. I then re-installed the new version and there are
still a lot of those errors.
I went back to the programming machine and went through all of the
references to see if any were missing... there were none missing. I then
programmed a few lines to show me the references on the runtime machines and
there were still no missing referrences.
I then installed the new version onto a completely virgin XP machine and
there were no errors. The problem is that I have to be able to install this
new version on machines that have the older version of my application but I
can't duplicate the error in the programming environment and the error
doesn't occur on a virgin machine. Both versions of my application were
developed with Access2003 using the 2003 runtime to distribute.
Why is this happening and what can I do to fix it? Its driving me nuts!
--TonyD--
(This same message was also posted in ...developers.toolkits and
....devtoolkits with no responses for 2 days... that's why I'm also posting it
here.)