PD Wizard - 2000 vs ME 1

[Niv3k]

I am building an application that needs to run on 98/NT/ME/2000... And by careful, minimized use of API's, it should. But of course, it doesn't. I use a Word object in the program, and that is where the compiled and installed program crashes on both ME and 98. Of course, it runs flawlessly on 2000 (can't test NT, cause I don't have an NT box lying around anymore)

Yes - it was compiled on 2000, and packaged with the PD Wizard.

Please help. - Also info on .MSI would be helpful.

Kevin

PS - Please remember those who died. And help those that are alive. Give blood, cash, clothes, blankets, whatever to the red cross. Sign an organ donor card. Freedom never dies.

 

[JohnYingling]

Did you do "early binding" by using a typelib? What version of Word supplied the TypeLib? Is it the same version on all systems?

When I compile a production version of a VB program that accesses Word, I change all references to Word objects to AS Object i.e. "Late Binding". As long as I haved not used features not present in al versions, it is backward and and forward compatible with all versions. My program runs om Win NT Workstation with Win '97, Win ME with Word 2000 and Win 200 Pro with Word 2000.

Microsoft now recommends "late binding" for out of process automation since they broke binary compatribility in Access 2000.

http://www.VBCompare.com

http://www.VBSortGen.com

 

[Niv3k]

AAAAAAARRRRRRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHH!

Yes, I used early binding.

Thanks.