VulcanJedi
Technical User
Writing VBA that is universally applicable? HOW? I work at a place where the network has a myriad of OS/, office packages? How do I know what will work where, ugh?! ![[yinyang]](/data/assets/smilies/yinyang.gif "[yinyang] [yinyang]")
Tranpkp ![[pc2]](/data/assets/smilies/pc2.gif "[pc2] [pc2]")
Tranpkp 
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VBA Combatibility?
- Thread starter VulcanJedi
- Start date
- Status
Hi Tranpkp!
That's what makes our job so much FUN!
I've found that, in general, the more your code stays within a single application (i.e. Word, Excel, etc), the more likely it is to operate correctly on another machine. In other words, if you avoid trying to do things like establish links between Excel and Word or reference a network drive, you are often fairly safe.
The other thing I usually do when working in an environment with multiple versions of Office installed is to write my code in Excel/Word 97. Stuff that runs in 97 USUALLY runs in 2000.
General thoughts, but I hope they help!
VBAjedi![[swords]](/data/assets/smilies/swords.gif "[swords] [swords]")
That's what makes our job so much FUN!
I've found that, in general, the more your code stays within a single application (i.e. Word, Excel, etc), the more likely it is to operate correctly on another machine. In other words, if you avoid trying to do things like establish links between Excel and Word or reference a network drive, you are often fairly safe.
The other thing I usually do when working in an environment with multiple versions of Office installed is to write my code in Excel/Word 97. Stuff that runs in 97 USUALLY runs in 2000.
General thoughts, but I hope they help!
VBAjedi
- Status
Similar threads
- Locked
- Helpful tip
