If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Conflict between packaged Access Applications
Hello everyone,
I have developed two database applications with Access 2007. I have used the package wizard and created setup.exe files. The problem is, I can't install these two applications in the same machine. Once I install one application, when I try to install the second one I get a message saying that the application is already installed. One appplication is for training the other one is an addressbook. Do I have to setup package wizard in a way that it won't use the same registry entry? How? P.S. the applications install in different directories and have different executable names. Thank you in advance, V. -- Desktop Solutions for Small Companies http://www.micromango.com Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#2
|
|||
|
|||
Conflict between packaged Access Applications
It doesn't look like anyone is going to reply to this so I will render my
opinion. I don't think this has anything to do with trying to install two apps. This system just doesn't work. You may be able to install an application one time, but after that forget it. That has been my experience. I had problem after problem and no one gave a response. I don't think there is a solution at this point in time. "vanleurth" u13147@uwe wrote in message news:82d40d9ead552@uwe... Hello everyone, I have developed two database applications with Access 2007. I have used the package wizard and created setup.exe files. The problem is, I can't install these two applications in the same machine. Once I install one application, when I try to install the second one I get a message saying that the application is already installed. One appplication is for training the other one is an addressbook. Do I have to setup package wizard in a way that it won't use the same registry entry? How? P.S. the applications install in different directories and have different executable names. Thank you in advance, V. -- Desktop Solutions for Small Companies http://www.micromango.com Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#3
|
|||
|
|||
Conflict between packaged Access Applications
Thank you Mark,
I think the package wizard doesn't really work. It whill be great if MS Access works as it is suppose to. I think I will drop MS Access development and move on to ASP.NET. Access has given me more than enough trouble for the last three years. V. Mark A. Sam wrote: It doesn't look like anyone is going to reply to this so I will render my opinion. I don't think this has anything to do with trying to install two apps. This system just doesn't work. You may be able to install an application one time, but after that forget it. That has been my experience. I had problem after problem and no one gave a response. I don't think there is a solution at this point in time. Hello everyone, [quoted text clipped - 19 lines] V. -- Desktop Solutions for Small Companies http://www.micromango.com Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#4
|
|||
|
|||
Conflict between packaged Access Applications
That's a shame. I think Access is outstanding, but at the same time it has
many issues to work around. The only experience I have with .Net is a couple of simple webpages I put up but no experience with Windows forms. If you are putting up a web application, I don't see how you can get functionality even close to what you can do in Access. I have never seen a webform that wasn't awkward and clumsy comared to Access. God Bless, Mark "vanleurth via AccessMonster.com" u13147@uwe wrote in message news:82e1aa351d024@uwe... Thank you Mark, I think the package wizard doesn't really work. It whill be great if MS Access works as it is suppose to. I think I will drop MS Access development and move on to ASP.NET. Access has given me more than enough trouble for the last three years. V. Mark A. Sam wrote: It doesn't look like anyone is going to reply to this so I will render my opinion. I don't think this has anything to do with trying to install two apps. This system just doesn't work. You may be able to install an application one time, but after that forget it. That has been my experience. I had problem after problem and no one gave a response. I don't think there is a solution at this point in time. Hello everyone, [quoted text clipped - 19 lines] V. -- Desktop Solutions for Small Companies http://www.micromango.com Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/200804/1 |
#5
|
|||
|
|||
Conflict between packaged Access Applications
P.S. the applications install in different directories and have different executable names. Thank you in advance, Did you "copy" your original package, and use save-as to create a "new" package for the 2nd one? (if yes, then you have to force the product id/number to change). I would try creating the 2nd different package from scratch (don't use an existing package, or as mentioned, for the product keys/id's to change. If you don't want to start from scratch, then use the space bar to erase the product id fields in the wizard, and then tab back in to the fields, and you see the product numbers change.... As mentioned, your MUCH better off to simply install the runtime SEPARATE from the applications part. Once you have the runtime installed, then you can simply "copy" any database to that machine (another words, don't use the package wizard for deployment your application, but use it for the installing of the runtime). I suspect your product keys info page is the same in both cases...... -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada |
Thread Tools | |
Display Modes | |
|
|