Thanks for that, I understand it better now. the problem is that the user of my applcation needs to also use outlook, that re-regsiters the newer version DLL even if my app copies another one during the installation.
I cant believe this of microsoft, if there are two different versions of comdlg32.ocx for win2k and Xp, and they are not backward compatabile, wtf is going on!?!?. I also use 2000 to program the application, and it is unacceptable for the user to have to "downgrade" to beable to use my app. if I did update the comdlg32.ocx on my system, will it still work in win2k? also, do you kow how I would register this component and replace the existing version? I think this could be an important point in the future, because as VB programmers, we cant expect our users cjust to keep using older versions of components. There musdt be a way of keeping up to date with these and maintaining our software. thks rnd ----- Original Message ----- From: "Matt Lorenz Jr" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, May 23, 2004 2:02 PM Subject: Re: [vbhelp] Common Dialog Control Uregent help needed.. > This happens when you move an executable from one OS to another rather than > actually installing your application. > > You have to install your app on the XP box and let your installation replace > the comdlg32.ocx and whatever else it needs. > > I know you are thinking that sucks - you are moving them from a newer > version of comdlg32.ocx to an older one. It is all you can do though, short > of rewriting your app to not use comdlg32.ocx. > > I have the same problem because I use Win2000 on my programming box. I have > not had any problems with my VB app breaking anything else on users' boxes > when replacing the comdlg32.ocx. > > > ----- Original Message ----- > From: "rnd" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, May 23, 2004 5:02 AM > Subject: [vbhelp] Common Dialog Control Uregent help needed.. > > > > My user gets an error message when he tries to run my application > > (Comdlg32.ocx wont load.. ) it appears he has a newer version on his XP > > system than the application was compiled with. > > > > Im not sure of the safety of just replacing the version I have with a > newer > > one if the application doesnt run. it could mess up everything.. > > > > Could this be a registry messup, SURELY microsoft ensured the backward > > compatiblity of this OCX.. and if not, why the hell not!! > > > > thanks in advance > > > > rnd > > > > > > > > > > '// ======================================================= > > Rules : http://ReliableAnswers.com/List/Rules.asp > > Home : http://groups.yahoo.com/group/vbHelp/ > > ======================================================= > > Post : [EMAIL PROTECTED] > > Join : [EMAIL PROTECTED] > > Leave : [EMAIL PROTECTED] > > '// ======================================================= > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > '// ======================================================= Rules : http://ReliableAnswers.com/List/Rules.asp Home : http://groups.yahoo.com/group/vbHelp/ ======================================================= Post : [EMAIL PROTECTED] Join : [EMAIL PROTECTED] Leave : [EMAIL PROTECTED] '// ======================================================= Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/vbhelp/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
