Jet Libraries...

  • Thread starter Thread starter Scott
  • Start date Start date
S

Scott

The problem is between Access 2002 and Access 2000, as
well as the OS file structure difference between XP Pro
and Win 2000.

You see, I develop in Access 2002, with a 2000 file
format, and I am installing the application on machines
with Office 2000. In the reference settings the Microsoft
Jet Replication and Objects library 2.6 is not available
on those machines. They use 2.5 instead.

I have the copyrights to this application and I set it up
as a user version so no one can have access to the code
and I want the ability to copy it to the machine without
having to convert it each time. It is already stretching
things by having to leave the menu options available for
linking the application to the server holding the
database tables because they are allowed access to the
tables.

I already tried bringing in the dll files, but my OS on
the development system is XP Pro and they mostly run Win
2000 and it is a different file structure. I don't know
where to put the files for them to be recognized.

Do you have any suggestions?

Best Regards,
Scott
 
Respondent,

I appreciate your reply, but you didn't seem to
understand what I was saying. The other computer doesn't
have the files because it is a completely different
Office version as well as a completely different OS file
structure. VBA can't find what isn't there.

Also, it is a DLL file not a DDL file, and, you cannot
create an object from one that doesn't exist. Besides
that, VBA doesn't know what objects are. They pretend
they do and create their own version of it with a ton of
hidden code we have to decipher later becuase it doesn't
realy behave as an object oriented perspective.

There is no object to create. I am searching for version
file resources so they can interact with each other and
it has nothing to do with the application, only Access
and its abilities to work with itself and its previous
versions.

Makes you wonder even more about just how much they
understand about object oriented programming, doesn't it?
They don't even have any API's to show their
understanding of it.

Once again, Thanks,
Scott
 
Scott said:
I set it up
as a user version so no one can have access to the code
Click to expand...

Yes, this is what any self respecting developer will do. In fact, if you
have any experience, you likely are distributing a mde.

and I want the ability to copy it to the machine without
having to convert it each time. It is already stretching
things by having to leave the menu options available for
linking the application to the server holding the
database tables because they are allowed access to the
tables.
Click to expand...

Gee, just about every regular here has placed their own custom code in their
start-up routines that checks if the back end location has changed, or is
not found. if the back end location is NOT found, then you no doubt ask the
user, and then pop up the standard windows file browse dialog. The user then
navigates to the backend location, and then you re-link. No self respecting
developer would require the users to see the tables, or even has to use the
wizards. And, in fact if using the runtime for distribution, you don't have
the linked able manager anyway (however..that is moot..as you really for a
good production application need to proved your own set of linking tools).
Both the code for re-linking the tables (without the wizard), and the code
to pop up the windows files dialog via the windows API is available at:

www.mvps.org/access

In at most a few hours you can build a nice custom re-linking system. And,
you can even make it work in the case that both the front end, and the back
end are in the same dir..and if the location is moved...it will re-link for
you automatically.

As for hiding the ms-access interface...you don't need any special code at
all anyway. (tools->startup can hide the access stuff).

I already tried bringing in the dll files, but my OS on
the development system is XP Pro and they mostly run Win
2000 and it is a different file structure. I don't know
where to put the files for them to be recognized.

Do you have any suggestions?
Click to expand...

If you are develping and deploying to clients running a2000, then you need
to be develping on a pc with the same version. I don't know of any other
appcltion develpment evneoment that this rule is any differnt. You never
could develop in VB6, and then try and deploy in VB5? Perahps I am missing
somting here?
 
Back
Top