M
mdas
Using Access 2k with references to Excel object 10.0 and DAO 3.6.
Okay, so I'm about to let this database out to coworkers as a small internal
application. I tried the database on another computer and had some big
problems.
Turns out that the Excel object 10.0 was missing and all that computer had
was Excel object 9.0. So I just go ahead and check that reference and it
looks good.
My concern is I send this out to a half dozen people and they all have
different problems (maybe some have DAO 3.5 instead of 3.6, etc.) How do I
minimize the potential headache of having to set references for the
different computers? Is there a way Access can tell me exaclty what is
missing via some error message? I know I can look at tools|references and
see that one says "Missing: ...", but I wanted to catch it when the form
opens -- it looks better. Right now, the form opens fine, but there are no
records in the combobox since I use the left() function and apparenlty that
needs the Excel object.
Finally, is there any way to include the necessary code within the .mdb
itself so that the end-user doesn't have to do all this setup? Are .olb
files like DLLs (run-time linking)?
Thanks!
-Mark
Okay, so I'm about to let this database out to coworkers as a small internal
application. I tried the database on another computer and had some big
problems.
Turns out that the Excel object 10.0 was missing and all that computer had
was Excel object 9.0. So I just go ahead and check that reference and it
looks good.
My concern is I send this out to a half dozen people and they all have
different problems (maybe some have DAO 3.5 instead of 3.6, etc.) How do I
minimize the potential headache of having to set references for the
different computers? Is there a way Access can tell me exaclty what is
missing via some error message? I know I can look at tools|references and
see that one says "Missing: ...", but I wanted to catch it when the form
opens -- it looks better. Right now, the form opens fine, but there are no
records in the combobox since I use the left() function and apparenlty that
needs the Excel object.
Finally, is there any way to include the necessary code within the .mdb
itself so that the end-user doesn't have to do all this setup? Are .olb
files like DLLs (run-time linking)?
Thanks!
-Mark