|
| 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 |
|
#11
February 8th, 2005, 02:41 AM
|
|||
|
|||
FWIW...I am a former MVP (2000)...and have worked with Access since v1.0.
Just because some people don't as much time to spend answering questions in NGs doesn't mean they know any less. Nevertheless, the advice to look into other installer technology stands...and I suspect most current MVPs would back me up on that. But you're welcome to find out the hard way. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... Does anyone else care to help me? Like an MVP? Thank you, Karen "Paul Overway" wrote in message ... If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the current user. That is why you're not seeing shortcuts for other accounts. FWIW..if you're really serious about distributing an Access app, you should look into other options for installer technology. The shortcoming you've encountered is just one of many. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... What do you mean by "My package"? My developer packaging wizard does not specify anything. As far as I remember, when creating a package using the packaging wizard, this question is never asked. If you mean does the workstation ask, it does not ask when installing, either. "Paul Overway" wrote in message ... OK...does your package specify that the install is for all users or just the current user? If you package is for current user, and you install it under the machine admin account, it wouldn't be available for all users. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... Sorry, why don't we just start with the most obvious: When I install as the machine's administrator, then log in as the user, click on Start, Programs...MyApp does not even show up. "MacDermott" wrote in message ... I understand that this must be very frustrating for you, but "errors all over the place" and "it bombs out" don't give us much to go on, either. Could you be more specific as to exactly what you're doing, and what the error messages you receive are? "Karen Hart" wrote in message k.net... Help!!! I have my runtime application installed on many network workstations that are running XP Operating System, Service Pack 1. I have them: 1. log in as the network and workstation administrator, 2. install my runtime app which I created with the packaging wizard, 3. run the Art2002Sp3-kb834693-client-enu.exe patch, 4. and then log in as the workstation user, who has your basic limited user rights to the workstation and network. 5. Click Start, Programs, MyApp. It runs great! Full functionality! No problems! The problem starts with workstations that are running XP Operating System, Service Pack TWO (with all patches up to date). After following steps 1-4, they click on Start, Programs, and MyApp does not show up! I've tried putting the shortcut on all desktops when logged in as administrator, then logging in as the user and trying to launch MyApp, but I get very wacky results with this. Errors all over the place when I try to do anything. I've tried logging in as the user and trying to install my setup.exe created by the packaging wizard, but of course since the user doesn't have administrative rights to the computer, it bombs out. I've tried giving the user administrative rights and installing. It installs, but again, as soon as I try to do the most basic tasks, like run a query, it starts erroring out. (Again, the same basic tasks that are functioning perfectly on the machines with Service Pack 1). Thank you in advance for any help, K. Hart 
|
|
#12
February 11th, 2005, 12:39 AM
|
|||
|
|||
|
I did not mean to offend anyone. It just seemed that someone on the
Microsoft newsgroup criticizing the Microsoft Packaging Wizard and suggesting that we need to use 3rd party products to install Microsoft apps seemed out of bounds. :-) "Fred Boer" wrote in message ... Dear Karen: Your comment: "Does anyone else care to help me? Like an MVP?" might be interpreted as a critique of the help you've been offered to this point. Was that your intention? You don't have to be designated an "MVP" to be an Access expert, and many knowledgeable and helpful posters here aren't MVPs!  Earlier in the thread, you were asked to describe the error messages you were getting, but you haven't given us the error numbers or error messages. To be precise: you mentioned one problem, which wasn't really an error but a setup issue. Careful descriptions of the errors and/or text of the error messages and/or error numbers would be helpful! I'm curious: you say that when you gave the user "Admin" permissions, the installation seemed to work, then you say that when you tried to run a query, "it starts erroring out.". Can we assume, then, that the *installation* problem is solved using this process? Could you describe exactly what is happening when "it starts erroring out."? Fred Boer (Definitely NOT an expert!) "Karen Hart" wrote in message ink.net... Does anyone else care to help me? Like an MVP? Thank you, Karen "Paul Overway" wrote in message ... If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the current user. That is why you're not seeing shortcuts for other accounts. FWIW..if you're really serious about distributing an Access app, you should look into other options for installer technology. The shortcoming you've encountered is just one of many. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... What do you mean by "My package"? My developer packaging wizard does not specify anything. As far as I remember, when creating a package using the packaging wizard, this question is never asked. If you mean does the workstation ask, it does not ask when installing, either. "Paul Overway" wrote in message ... OK...does your package specify that the install is for all users or just the current user? If you package is for current user, and you install it under the machine admin account, it wouldn't be available for all users. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... Sorry, why don't we just start with the most obvious: When I install as the machine's administrator, then log in as the user, click on Start, Programs...MyApp does not even show up. "MacDermott" wrote in message ... I understand that this must be very frustrating for you, but "errors all over the place" and "it bombs out" don't give us much to go on, either. Could you be more specific as to exactly what you're doing, and what the error messages you receive are? "Karen Hart" wrote in message k.net... Help!!! I have my runtime application installed on many network workstations that are running XP Operating System, Service Pack 1. I have them: 1. log in as the network and workstation administrator, 2. install my runtime app which I created with the packaging wizard, 3. run the Art2002Sp3-kb834693-client-enu.exe patch, 4. and then log in as the workstation user, who has your basic limited user rights to the workstation and network. 5. Click Start, Programs, MyApp. It runs great! Full functionality! No problems! The problem starts with workstations that are running XP Operating System, Service Pack TWO (with all patches up to date). After following steps 1-4, they click on Start, Programs, and MyApp does not show up! I've tried putting the shortcut on all desktops when logged in as administrator, then logging in as the user and trying to launch MyApp, but I get very wacky results with this. Errors all over the place when I try to do anything. I've tried logging in as the user and trying to install my setup.exe created by the packaging wizard, but of course since the user doesn't have administrative rights to the computer, it bombs out. I've tried giving the user administrative rights and installing. It installs, but again, as soon as I try to do the most basic tasks, like run a query, it starts erroring out. (Again, the same basic tasks that are functioning perfectly on the machines with Service Pack 1). Thank you in advance for any help, K. Hart
|
|
#13
February 11th, 2005, 01:08 AM
|
|||
|
|||
|
Karen Hart wrote:
I did not mean to offend anyone. It just seemed that someone on the Microsoft newsgroup criticizing the Microsoft Packaging Wizard and suggesting that we need to use 3rd party products to install Microsoft apps seemed out of bounds. :-) Did you want help or a sales pitch? The truth is that Microsoft has been consistently making the developer's tools more and more irrelevent with each version change. IMO this has been deliberate. -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com
|
|
#14
February 11th, 2005, 03:36 PM
|
|||
|
|||
|
Hi Karen,
So long as it's about Access technical issues, just about anything goes in this newsgroup. There are some interesting observations on "netiquette" at www.mvps.org/access Any number of people might have given voice to the same opinions that Fred did, MVP or not. You might check out the developers.toolkitode or devtoolkits newsgroups for opinions on installations. If something MS delivers to support us in our development efforts isn't up to par then let it be known so that someone struggling along (and alone) doesn't continue in ignorance. If there are better competitive products for the same function, let that be known too. Before people went looking elsewhere they tried to get positive responses from Microsoft. Microsoft says that there's no problem that they intend to fix. I read these newsgroups offline. When I saw your request for the services of an MVP I simply deleted your post and went looking for someone I could help. :-) When you get your current issue resolved you might make it a point to take a break from the regular grind for a few minutes and check into these newsgroups to see if there is someone you could help. It takes you out of your own little world for a while and gives you a different perspective. HTH -- -Larry- -- "Karen Hart" wrote in message ink.net... I did not mean to offend anyone. It just seemed that someone on the Microsoft newsgroup criticizing the Microsoft Packaging Wizard and suggesting that we need to use 3rd party products to install Microsoft apps seemed out of bounds. :-) "Fred Boer" wrote in message ... Dear Karen: Your comment: "Does anyone else care to help me? Like an MVP?" might be interpreted as a critique of the help you've been offered to this point. Was that your intention? You don't have to be designated an "MVP" to be an Access expert, and many knowledgeable and helpful posters here aren't MVPs! Earlier in the thread, you were asked to describe the error messages you were getting, but you haven't given us the error numbers or error messages. To be precise: you mentioned one problem, which wasn't really an error but a setup issue. Careful descriptions of the errors and/or text of the error messages and/or error numbers would be helpful! I'm curious: you say that when you gave the user "Admin" permissions, the installation seemed to work, then you say that when you tried to run a query, "it starts erroring out.". Can we assume, then, that the *installation* problem is solved using this process? Could you describe exactly what is happening when "it starts erroring out."? Fred Boer (Definitely NOT an expert!) "Karen Hart" wrote in message ink.net... Does anyone else care to help me? Like an MVP? Thank you, Karen "Paul Overway" wrote in message ... If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the current user. That is why you're not seeing shortcuts for other accounts. FWIW..if you're really serious about distributing an Access app, you should look into other options for installer technology. The shortcoming you've encountered is just one of many. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... What do you mean by "My package"? My developer packaging wizard does not specify anything. As far as I remember, when creating a package using the packaging wizard, this question is never asked. If you mean does the workstation ask, it does not ask when installing, either. "Paul Overway" wrote in message ... OK...does your package specify that the install is for all users or just the current user? If you package is for current user, and you install it under the machine admin account, it wouldn't be available for all users. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... Sorry, why don't we just start with the most obvious: When I install as the machine's administrator, then log in as the user, click on Start, Programs...MyApp does not even show up. "MacDermott" wrote in message ... I understand that this must be very frustrating for you, but "errors all over the place" and "it bombs out" don't give us much to go on, either. Could you be more specific as to exactly what you're doing, and what the error messages you receive are? "Karen Hart" wrote in message k.net... Help!!! I have my runtime application installed on many network workstations that are running XP Operating System, Service Pack 1. I have them: 1. log in as the network and workstation administrator, 2. install my runtime app which I created with the packaging wizard, 3. run the Art2002Sp3-kb834693-client-enu.exe patch, 4. and then log in as the workstation user, who has your basic limited user rights to the workstation and network. 5. Click Start, Programs, MyApp. It runs great! Full functionality! No problems! The problem starts with workstations that are running XP Operating System, Service Pack TWO (with all patches up to date). After following steps 1-4, they click on Start, Programs, and MyApp does not show up! I've tried putting the shortcut on all desktops when logged in as administrator, then logging in as the user and trying to launch MyApp, but I get very wacky results with this. Errors all over the place when I try to do anything. I've tried logging in as the user and trying to install my setup.exe created by the packaging wizard, but of course since the user doesn't have administrative rights to the computer, it bombs out. I've tried giving the user administrative rights and installing. It installs, but again, as soon as I try to do the most basic tasks, like run a query, it starts erroring out. (Again, the same basic tasks that are functioning perfectly on the machines with Service Pack 1). Thank you in advance for any help, K. Hart
|
|
#15
February 11th, 2005, 07:41 PM
|
|||
|
|||
|
On Fri, 11 Feb 2005 00:39:40 GMT, "Karen Hart"
wrote: I did not mean to offend anyone. It just seemed that someone on the Microsoft newsgroup criticizing the Microsoft Packaging Wizard and suggesting that we need to use 3rd party products to install Microsoft apps seemed out of bounds. :-) No way. One of the strengths of these newsgroups is that there's no pressure to pretend Microsoft is perfect. -- John Nurick [Microsoft Access MVP] Please respond in the newgroup and not by email.
|
|
#16
February 11th, 2005, 08:08 PM
|
|||
|
|||
|
Dear Karen:
I did not mean to offend anyone. Good! Now, putting all the rest of this aside, have you resolved your problem yet? If not, how about trying again to describe the situation, particularly the details of error messages (as per my last post). I am not an expert, and a solution is unlikely to come from me, but someone probably will be able to fine one - I've rarely (never?) seen the volunteers here stumped! Cheers! Fred Boer
|
|
#17
February 11th, 2005, 09:03 PM
|
|||
|
|||
|
I'm very sorry to have offended you, Paul. I appreciate your offer to help.
Karen "Paul Overway" wrote in message ... FWIW...I am a former MVP (2000)...and have worked with Access since v1.0. Just because some people don't as much time to spend answering questions in NGs doesn't mean they know any less. Nevertheless, the advice to look into other installer technology stands...and I suspect most current MVPs would back me up on that. But you're welcome to find out the hard way. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... Does anyone else care to help me? Like an MVP? Thank you, Karen "Paul Overway" wrote in message ... If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the current user. That is why you're not seeing shortcuts for other accounts. FWIW..if you're really serious about distributing an Access app, you should look into other options for installer technology. The shortcoming you've encountered is just one of many. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... What do you mean by "My package"? My developer packaging wizard does not specify anything. As far as I remember, when creating a package using the packaging wizard, this question is never asked. If you mean does the workstation ask, it does not ask when installing, either. "Paul Overway" wrote in message ... OK...does your package specify that the install is for all users or just the current user? If you package is for current user, and you install it under the machine admin account, it wouldn't be available for all users. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... Sorry, why don't we just start with the most obvious: When I install as the machine's administrator, then log in as the user, click on Start, Programs...MyApp does not even show up. "MacDermott" wrote in message ... I understand that this must be very frustrating for you, but "errors all over the place" and "it bombs out" don't give us much to go on, either. Could you be more specific as to exactly what you're doing, and what the error messages you receive are? "Karen Hart" wrote in message k.net... Help!!! I have my runtime application installed on many network workstations that are running XP Operating System, Service Pack 1. I have them: 1. log in as the network and workstation administrator, 2. install my runtime app which I created with the packaging wizard, 3. run the Art2002Sp3-kb834693-client-enu.exe patch, 4. and then log in as the workstation user, who has your basic limited user rights to the workstation and network. 5. Click Start, Programs, MyApp. It runs great! Full functionality! No problems! The problem starts with workstations that are running XP Operating System, Service Pack TWO (with all patches up to date). After following steps 1-4, they click on Start, Programs, and MyApp does not show up! I've tried putting the shortcut on all desktops when logged in as administrator, then logging in as the user and trying to launch MyApp, but I get very wacky results with this. Errors all over the place when I try to do anything. I've tried logging in as the user and trying to install my setup.exe created by the packaging wizard, but of course since the user doesn't have administrative rights to the computer, it bombs out. I've tried giving the user administrative rights and installing. It installs, but again, as soon as I try to do the most basic tasks, like run a query, it starts erroring out. (Again, the same basic tasks that are functioning perfectly on the machines with Service Pack 1). Thank you in advance for any help, K. Hart
|
|
#18
February 11th, 2005, 10:04 PM
|
|||
|
|||
|
I wasn't really offended. In fact, I probably wouldn't have been if Fred
hadn't suggested I should be.  )In respect to the real topic, you might want to check out the white paper on site below for alternative/inexpensive installers that are less problematic than what PDW generates. I have not yet had a customer call about failed install (except of my own doing) since I canned PDW. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... I'm very sorry to have offended you, Paul. I appreciate your offer to help. Karen "Paul Overway" wrote in message ... FWIW...I am a former MVP (2000)...and have worked with Access since v1.0. Just because some people don't as much time to spend answering questions in NGs doesn't mean they know any less. Nevertheless, the advice to look into other installer technology stands...and I suspect most current MVPs would back me up on that. But you're welcome to find out the hard way. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... Does anyone else care to help me? Like an MVP? Thank you, Karen "Paul Overway" wrote in message ... If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the current user. That is why you're not seeing shortcuts for other accounts. FWIW..if you're really serious about distributing an Access app, you should look into other options for installer technology. The shortcoming you've encountered is just one of many. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... What do you mean by "My package"? My developer packaging wizard does not specify anything. As far as I remember, when creating a package using the packaging wizard, this question is never asked. If you mean does the workstation ask, it does not ask when installing, either. "Paul Overway" wrote in message ... OK...does your package specify that the install is for all users or just the current user? If you package is for current user, and you install it under the machine admin account, it wouldn't be available for all users. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... Sorry, why don't we just start with the most obvious: When I install as the machine's administrator, then log in as the user, click on Start, Programs...MyApp does not even show up. "MacDermott" wrote in message ... I understand that this must be very frustrating for you, but "errors all over the place" and "it bombs out" don't give us much to go on, either. Could you be more specific as to exactly what you're doing, and what the error messages you receive are? "Karen Hart" wrote in message k.net... Help!!! I have my runtime application installed on many network workstations that are running XP Operating System, Service Pack 1. I have them: 1. log in as the network and workstation administrator, 2. install my runtime app which I created with the packaging wizard, 3. run the Art2002Sp3-kb834693-client-enu.exe patch, 4. and then log in as the workstation user, who has your basic limited user rights to the workstation and network. 5. Click Start, Programs, MyApp. It runs great! Full functionality! No problems! The problem starts with workstations that are running XP Operating System, Service Pack TWO (with all patches up to date). After following steps 1-4, they click on Start, Programs, and MyApp does not show up! I've tried putting the shortcut on all desktops when logged in as administrator, then logging in as the user and trying to launch MyApp, but I get very wacky results with this. Errors all over the place when I try to do anything. I've tried logging in as the user and trying to install my setup.exe created by the packaging wizard, but of course since the user doesn't have administrative rights to the computer, it bombs out. I've tried giving the user administrative rights and installing. It installs, but again, as soon as I try to do the most basic tasks, like run a query, it starts erroring out. (Again, the same basic tasks that are functioning perfectly on the machines with Service Pack 1). Thank you in advance for any help, K. Hart
|
|
#19
February 12th, 2005, 03:09 AM
|
|||
|
|||
|
We all live and learn... No worries!
I know my initial explanation was lame as to the vagueness of 'erroring out.' I was working second hand off of an end user's complaint, and doing the best I could to explain the problem. The end user seems to have resolved the problem, but I have been unable to contact him to get further details. As soon as I do, I will be happy to share. Enjoy the weekend, Karen "Fred Boer" wrote in message ... Oh, so it's *my* fault! g Well... perhaps you are right. Next time I get the urge to meddle I'll do one of those Dr. Evil lip-zips on myself! Best wishes to all... and to all a good night! Fred "Paul Overway" wrote in message ... I wasn't really offended. In fact, I probably wouldn't have been if Fred hadn't suggested I should be. )In respect to the real topic, you might want to check out the white paper on site below for alternative/inexpensive installers that are less problematic than what PDW generates. I have not yet had a customer call about failed install (except of my own doing) since I canned PDW. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... I'm very sorry to have offended you, Paul. I appreciate your offer to help. Karen "Paul Overway" wrote in message ... FWIW...I am a former MVP (2000)...and have worked with Access since v1.0. Just because some people don't as much time to spend answering questions in NGs doesn't mean they know any less. Nevertheless, the advice to look into other installer technology stands...and I suspect most current MVPs would back me up on that. But you're welcome to find out the hard way. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... Does anyone else care to help me? Like an MVP? Thank you, Karen "Paul Overway" wrote in message ... If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the current user. That is why you're not seeing shortcuts for other accounts. FWIW..if you're really serious about distributing an Access app, you should look into other options for installer technology. The shortcoming you've encountered is just one of many. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... What do you mean by "My package"? My developer packaging wizard does not specify anything. As far as I remember, when creating a package using the packaging wizard, this question is never asked. If you mean does the workstation ask, it does not ask when installing, either. "Paul Overway" wrote in message ... OK...does your package specify that the install is for all users or just the current user? If you package is for current user, and you install it under the machine admin account, it wouldn't be available for all users. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... Sorry, why don't we just start with the most obvious: When I install as the machine's administrator, then log in as the user, click on Start, Programs...MyApp does not even show up. "MacDermott" wrote in message ... I understand that this must be very frustrating for you, but "errors all over the place" and "it bombs out" don't give us much to go on, either. Could you be more specific as to exactly what you're doing, and what the error messages you receive are? "Karen Hart" wrote in message k.net... Help!!! I have my runtime application installed on many network workstations that are running XP Operating System, Service Pack 1. I have them: 1. log in as the network and workstation administrator, 2. install my runtime app which I created with the packaging wizard, 3. run the Art2002Sp3-kb834693-client-enu.exe patch, 4. and then log in as the workstation user, who has your basic limited user rights to the workstation and network. 5. Click Start, Programs, MyApp. It runs great! Full functionality! No problems! The problem starts with workstations that are running XP Operating System, Service Pack TWO (with all patches up to date). After following steps 1-4, they click on Start, Programs, and MyApp does not show up! I've tried putting the shortcut on all desktops when logged in as administrator, then logging in as the user and trying to launch MyApp, but I get very wacky results with this. Errors all over the place when I try to do anything. I've tried logging in as the user and trying to install my setup.exe created by the packaging wizard, but of course since the user doesn't have administrative rights to the computer, it bombs out. I've tried giving the user administrative rights and installing. It installs, but again, as soon as I try to do the most basic tasks, like run a query, it starts erroring out. (Again, the same basic tasks that are functioning perfectly on the machines with Service Pack 1). Thank you in advance for any help, K. Hart
|
|
#20
February 12th, 2005, 05:46 AM
|
|||
|
|||
|
Oh, so it's *my* fault! g Well... perhaps you are right. Next time I get
the urge to meddle I'll do one of those Dr. Evil lip-zips on myself! Best wishes to all... and to all a good night! Fred "Paul Overway" wrote in message ... I wasn't really offended. In fact, I probably wouldn't have been if Fred hadn't suggested I should be. )In respect to the real topic, you might want to check out the white paper on site below for alternative/inexpensive installers that are less problematic than what PDW generates. I have not yet had a customer call about failed install (except of my own doing) since I canned PDW. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... I'm very sorry to have offended you, Paul. I appreciate your offer to help. Karen "Paul Overway" wrote in message ... FWIW...I am a former MVP (2000)...and have worked with Access since v1.0. Just because some people don't as much time to spend answering questions in NGs doesn't mean they know any less. Nevertheless, the advice to look into other installer technology stands...and I suspect most current MVPs would back me up on that. But you're welcome to find out the hard way. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message ink.net... Does anyone else care to help me? Like an MVP? Thank you, Karen "Paul Overway" wrote in message ... If I remember correctly, the 2002 PDW ALWAYS installs shortcuts under the current user. That is why you're not seeing shortcuts for other accounts. FWIW..if you're really serious about distributing an Access app, you should look into other options for installer technology. The shortcoming you've encountered is just one of many. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... What do you mean by "My package"? My developer packaging wizard does not specify anything. As far as I remember, when creating a package using the packaging wizard, this question is never asked. If you mean does the workstation ask, it does not ask when installing, either. "Paul Overway" wrote in message ... OK...does your package specify that the install is for all users or just the current user? If you package is for current user, and you install it under the machine admin account, it wouldn't be available for all users. -- Paul Overway Logico Solutions http://www.logico-solutions.com "Karen Hart" wrote in message nk.net... Sorry, why don't we just start with the most obvious: When I install as the machine's administrator, then log in as the user, click on Start, Programs...MyApp does not even show up. "MacDermott" wrote in message ... I understand that this must be very frustrating for you, but "errors all over the place" and "it bombs out" don't give us much to go on, either. Could you be more specific as to exactly what you're doing, and what the error messages you receive are? "Karen Hart" wrote in message k.net... Help!!! I have my runtime application installed on many network workstations that are running XP Operating System, Service Pack 1. I have them: 1. log in as the network and workstation administrator, 2. install my runtime app which I created with the packaging wizard, 3. run the Art2002Sp3-kb834693-client-enu.exe patch, 4. and then log in as the workstation user, who has your basic limited user rights to the workstation and network. 5. Click Start, Programs, MyApp. It runs great! Full functionality! No problems! The problem starts with workstations that are running XP Operating System, Service Pack TWO (with all patches up to date). After following steps 1-4, they click on Start, Programs, and MyApp does not show up! I've tried putting the shortcut on all desktops when logged in as administrator, then logging in as the user and trying to launch MyApp, but I get very wacky results with this. Errors all over the place when I try to do anything. I've tried logging in as the user and trying to install my setup.exe created by the packaging wizard, but of course since the user doesn't have administrative rights to the computer, it bombs out. I've tried giving the user administrative rights and installing. It installs, but again, as soon as I try to do the most basic tasks, like run a query, it starts erroring out. (Again, the same basic tasks that are functioning perfectly on the machines with Service Pack 1). Thank you in advance for any help, K. Hart
|
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Should I install XP Service Pack 3 on a Windows 2000 machine? | Old White Haired Guy | Calendar | 1 | October 31st, 2004 05:33 PM |
| microsoft service pack 3. | hopekat | Running & Setting Up Queries | 3 | October 13th, 2004 02:39 AM |
| Service Pack Version 2 Problems | Jeannine | General Discussion | 2 | September 30th, 2004 08:02 PM |
| Is the Office Service Pack too much for me? | Norm | New Users | 7 | April 27th, 2004 07:59 PM |
| Excel / service pack bug ? | Dmitri Shvetsov | Setting up and Configuration | 1 | January 1st, 2004 11:53 PM |
Linear Mode
