Runtime Errors

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Tony - 05 May 2005 21:22 GMT

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.)

Reply to this Message

jl5000 - 05 May 2005 22:36 GMT

You need to uninstall the old version in the "non-virgin" machines before you
install the new one, I recommend you have a version control so you can have
each original setup for each of your versions, because windows requires the
original *.msi file, if you overwrote your original version, then you'll need
to change the name of the application in the package wizard and then
implement the application, do not forget the version control, I went nuts as
well with this problem

Signature

jl5000
<a href="http://joshdev.com"></a>

> 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
[quoted text clipped - 23 lines]
> ...devtoolkits with no responses for 2 days... that's why I'm also posting it
> here.)

Reply to this Message

Tony - 05 May 2005 22:52 GMT

Josh,

That makes sense. Do you mean I should change the "Title" of the
installation or change the actual name of the MDB file? Also, what do you
mean by "version control"?
--Tony--

> You need to uninstall the old version in the "non-virgin" machines before you
> install the new one, I recommend you have a version control so you can have
[quoted text clipped - 31 lines]
> > ...devtoolkits with no responses for 2 days... that's why I'm also posting it
> > here.)

Reply to this Message

jl5000 - 06 May 2005 17:41 GMT

Yes, Change the Title of the installation,

Here is what I do for Version Control:

-Create a folder for the application (like My_App)
-Then I create a subfolder for the first time I'm developing the application
(like My_App\Version_2005_05)
-Create subfolders to save all the user requests and installation package
-When a major change is needed I create another folder (Like
My_App\Version_2005_06) and copy the previous source database, and so on

I hope this helps,

Signature

jl5000
<a href="http://joshdev.com"></a>

> Josh,
>
[quoted text clipped - 38 lines]
> > > ...devtoolkits with no responses for 2 days... that's why I'm also posting it
> > > here.)

Reply to this Message