By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,665 Members | 2,802 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,665 IT Pros & Developers. It's quick & easy.

Compact MDB back to Access 97 format with code?

P: n/a
Hi Everyone,

I have a need to build a simple tool in Access 97 for my work that
will allow someone to convert a database (supplied externally) back to
an Access 97 format mdb file.

The files only contain data, no forms, reports, code or even
relationships. These source databases are the output from an external
ETL system over which we have no control. I know it is possible to
compact forward with JRO to newer verions of JET, but I was fairly
certain that going backward isnt possible....

I was thinking that perhaps I need to write some custom code to 'read'
the table structures from the source db with ADO and then to re-create
them in the target db making sure that the target db is created in 97
format. Once the structures are done then read the data from the
source and write the data back to the target. Seems a painful way to
do this if there is a way to successfully do the 'compact' trick.

Can anyone shed some light on this one?

Cheers

The Frog
Feb 6 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hi Tony,

I like the idea, but perhaps I am doing something wrong here. I cant
seem to get the DAO3.6 dll's to work with A97. When I go to tools-
references while screwing around with a module and change the
reference I get a lock-up with Access97. I am guessing that it is the
way our corporate pc images are set-up. This therefore also means
(most likely) that I wont be able to do anything about it.

The other issue is that I will have no idea of the tablenames or
structures when they are delivered, and because I cant open the DB in
A97 to easily read these I guess I am going to have to do this all
from code.

In the short term I am going to use KETTLE to do the data pumping for
me. Its a nice and free (and quite capable) ETL tool. I'll just set up
a blank A97 format DB to act as the container to receive the tables /
data, then l let KETTLE do all the work including making the tables.
It will get me by for now until I make an app to do the job for me
(specify source file - specify destination file and format, click go).

Thanks for the attempt Tony, I appreciate the effort.

Cheers

The Frog
Feb 8 '08 #2

P: n/a
The Frog <Mr************@googlemail.comwrote:
>I like the idea, but perhaps I am doing something wrong here. I cant
seem to get the DAO3.6 dll's to work with A97. When I go to tools-
references while screwing around with a module and change the
reference I get a lock-up with Access97. I am guessing that it is the
way our corporate pc images are set-up. This therefore also means
(most likely) that I wont be able to do anything about it.
No idea as I've never tried this myself. Did I forget to mention that? I just
recall someone statnig once that they were using DAO 3.6 DLLs in A97.
>The other issue is that I will have no idea of the tablenames or
structures when they are delivered, and because I cant open the DB in
A97 to easily read these I guess I am going to have to do this all
from code.
Yes, that would be a pain. You can run through the collections and such but still a
lot of code.
>In the short term I am going to use KETTLE to do the data pumping for
me. Its a nice and free (and quite capable) ETL tool. I'll just set up
a blank A97 format DB to act as the container to receive the tables /
data, then l let KETTLE do all the work including making the tables.
It will get me by for now until I make an app to do the job for me
(specify source file - specify destination file and format, click go).
Sounds like an interesting tool.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Feb 8 '08 #3

P: n/a
Thanks for the help guys. It turns out that the corporate pc image is
the root cause of the DAO3.6 not working. Nice trick, helps to have it
properly installed though :-)

Cheers

The Frog
Feb 11 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.