converting code to 64bit

[markjkubicki]

It wasn't till this week that I realized how long I've been ducking this issue...


Till now, I've simply had everyone uninstall their 64bit Access from office, and download the 32bit runtime version... (admittedly, a patch, but effective)

It's come time to bite the bullet and convert to 64 bit; add the "what version are you using" code, and all the related caveats

When this problem first showed up, I was able to find several articles and forums on declarations, long vs. short, and all those necessary things to know / do...
Today, I'm finding stupid.

Would someone (please) direct me to the correct aisle in the library stacks?

big thanks in advance,
mark

[rpeare]

I think what you're after is declaring your variables in what's called 'late binding' in other words, if for instance you are using MS outlook objects in your code and it's bombing out because you have an outdated reference in your code a late binding would (or should), from what I've read, assume you mean to use whatever reference is the 'current' one on the host PC.

Example using filesystem object

Early binding:
dim fs as FileSystemObject
set fs = new filesystemobject

debug.print x.getspecialfolder(0)


Late binding:
dim fs
set fs = createobject("scripting.filesystemobject")

debug.print x.getspecialfolder(0)

I don't know if this will solve your problem or not as I only learned the nomenclature for this a few weeks ago! I have done everything with late binding without knowing the proper term just because it was easier for me to get things working the way I wanted.