2003 VB Excel back to 2000 VB Excel

[MFlanders]

I have vb excel that I wrote in version 2000. When my company upgraded my PC
to v2003 I had no problems - all my programs ran just fine. However several
of my fellow employees are still running v2000 and when they attemp to run my
programs - they get a "Compile error: Can't find project or library" error.
Short of paying to have them all upgraded, is there a simple solutions so my
programs will run in v2000?

Thanks in advance,
Mike

 

[Jim Rech]

On a user's machine look at Tools, References in the VBE when your project
is active and determine which one is "missing". Uncheck it and the code may
run fine. If so it's not needed so uncheck it on your machine for future
installs.

--
Jim
|I have vb excel that I wrote in version 2000. When my company upgraded my
PC
| to v2003 I had no problems - all my programs ran just fine. However
several
| of my fellow employees are still running v2000 and when they attemp to run
my
| programs - they get a "Compile error: Can't find project or library"
error.
| Short of paying to have them all upgraded, is there a simple solutions so
my
| programs will run in v2000?
|
| Thanks in advance,
| Mike

 

[MFlanders]

Thanks Jim - that worked great. But now can I ever make changes to my
program from my PC with v2003? I control the main file and others access it
via a link in another software. Should I back load v2000 and always make
changes there so as to not gig everyone else?

Mike

 

[Chip Pearson]

You should be able to work on the workbook in 2003 even if the users
have only 2000. Just be sure not to use any features added post-2000.
If you are using non-standard DLLs, you'll have to copy those files to
the end-users' computers and register them with Windows using
Regsvr32. But if you have just a simple self-contained workbook, you
can work in 2003 without problems.

Cordially,
Chip Pearson
Microsoft MVP
Excel Product Group
Pearson Software Consulting, LLC
www.cpearson.com
(email on web site)

 

[Ken Wright]

If you are suporting users on a different version, the safest way to test is
to load that version on your machine as well and then try it yourself. Code
in 2003 if you want, but test in 2000. You can have as many versions of
office installed as you like (only one version of outlook though), but
should install in order, so if you install 2000 now, you should then
reinstall or repair 2003.

Note that this wouldn't necessarily have trapped this particular issue, but
the advice still holds good in general.

Regards
Ken...............................

 

[Simon Murphy]

Mike
if you are referencing external components (which it sounds like you are
from the missing library errors) then ideally you should develop on a
machine with the oldest version of Excel and Internet Explorer and
Windows. Otherwise this problem will keep cropping up.

You can't roll your box back by just installing 2000 as various OS
components will have been updated and won't get downgraded. Well it
might work - it totally depends what components your code is referencing.

Another option which I have used in the past is to remove the references
and declare the variables referring to external components as Objects eg:
Dim cat as ADOX.Catalog 'for my machine
Dim cat as Object ' for their machine.

Then comment out the objects and add the refs for developing and
testing. For release remove refs and swap comment lines. This executes a
bit slower, so may not suit your situation.

You could use conditional compilation if the code is complex.

There is a reference checker here I have found useful:
http://www.codematic.net/excel-tools/free-excel-tools.htm

If you are working with data make sure everyone has the latest mdac (and
IE if poss)

Cheers
Simon
Excel development website: www.codematic.net