Porting and different version of components


Hello group,

I'm porting an Excel Application (VBA) from Office 2003 to 2000. After checking References under Tools in VBE I see

Excel 2003 is equipped with:

Microsoft Excel 11.0 Object Library
Microsoft Office 11.0 Object Library
Microsoft Calender 11.0 Object Library
Microsoft Windows Common Control 6.0 (SP6)
fptdc 1.0 type library


and Excel 2000 has:

Microsoft Excel 9.0 Object Library
Microsoft Office 9.0 Object Library
Microsoft Calender 9.0 Object Library
Microsoft Windows Common Control 6.0 (SP4)
DOESN'T HAVE fptdc !


My question is what should I do in order to make my application to run without problem regardless of different  version of the above components?


regards,
ak
akohanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dirknibleckCommented:
I suspect that your application will continue to work if you uncheck the box on fptdc in 2003. But I don't know how this would affect 2000. I would try it and see. A quick google on the library shows someone else who had a problem with this in Access, and unchecking it solved his problem.
0
akohanAuthor Commented:


No, I haven't unchecked it in 2003 version. What I was trying to say is that the 2000 version doesn't have it on its list. My major goal is to make the application run on Excel 2000 as well.

Thanks for your response.

regards,
ak
0
Rory ArchibaldCommented:
You should develop on the earliest version you expect the code to run on, and have the references set accordingly. Calendar controls can be particularly temperamental about version issues, so you will have to test to see what works. If necessary you will need an installer and to include any specific controls you require in the package, as long as you have suitable licences to redistribute them.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

akohanAuthor Commented:

Thanks but I didn't get my answer yet. Does anybody have any advice?

Regards,
ak
0
dirknibleckCommented:
What are you using this library for?

It appears to be a FrontPage control. Unless you are doing something in your vba that utilizes FrontPage, I would be surprised if you couldn't uncheck the reference from the 2003 version and have the program run fine in both 2000 and 2003.

Otherwise, did you try Rory's answer? You can package your Excel file with the References so that it will run in any version, however it involves pushing an install file to your users.
0
dirknibleckCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dirknibleckCommented:
This link provides more information on your problem as well:

http://www.mcse.ms/message2115630.html
0
akohanAuthor Commented:


Thanks all.

regards,
ak
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Office

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.