Hi,
I have to copy a lot of queries out of a access 97 database in to another
access 97 database. Their is at least one corrupt table in the database.
I would like to get the tables as well but can live with it if I need to
recreate them.
Yes it has to be in access 97 - very bad move

Any suggestions

Thanks MarkS

If the question is how to copy queries from one MDB to another, then open the
new MDB and import all the queries from the Old MDB to the new one.
You can also import the tables, you might get an error message when trying
to import the corrupt table.

Also, have you tried Compact and Repair on the old MDB?
In any case, create a back up to your data base before you try anything.

--
Good Luck
BS"D


"MarkS" wrote:

> Hi,
> I have to copy a lot of queries out of a access 97 database in to another
> access 97 database. Their is at least one corrupt table in the database.
> I would like to get the tables as well but can live with it if I need to
> recreate them.
> Yes it has to be in access 97 - very bad move
>
> Any suggestions
>
> Thanks MarkS

Maybe there is something you are not telling us, but what's wrong with
File - Get External Data -Import?

Why is Access 97 a very bad move?

"MarkS" <(E-Mail Removed)> wrote in message
news:1F58AB48-46D2-4F8E-8A75-(E-Mail Removed)...
> Hi,
> I have to copy a lot of queries out of a access 97 database in to another
> access 97 database. Their is at least one corrupt table in the database.
> I would like to get the tables as well but can live with it if I need to
> recreate them.
> Yes it has to be in access 97 - very bad move
>
> Any suggestions
>
> Thanks MarkS

On Mon, 28 May 2007 00:43:03 -0700, MarkS <(E-Mail Removed)>
wrote:

>Hi,
>I have to copy a lot of queries out of a access 97 database in to another
>access 97 database. Their is at least one corrupt table in the database.
>I would like to get the tables as well but can live with it if I need to
>recreate them.
>Yes it has to be in access 97 - very bad move

Actually 97 is still the best, most stable version of Access out there.

As noted elsethread, File... Get External Data... Import should work fine with
your queries, even with a corrupt table. You can also import Forms, Reports
and code, and the undamaged tables. Depending on *how* the table is corrupted,
you may be able to salvage the data; one technique is to import the table,
*design mode only*; then use File... Get External Data... Link to link to it,
and run an Append query to append the undamaged records. You do need to use
criteria on the table's Primary Key to select records known to be undamaged -
if it's a corrupt Memo field then you should NOT apply any criteria to the
memo field. Instead, identify the damaged record and use a range of ID values
so that the damage record is not touched. For example, if you know that the
record with ID 3155 is corrupt, use a criterion

<= 3154 OR >= 3156

to "touch" only undamaged records.

John W. Vinson [MVP]

I didn't know the import function was in Access 97, as the IT department has
removed it and a lot of the other functions. Have asked to get it installed,
this removal of functions is why I am not happy with it

Thanks

"John W. Vinson" wrote:

> On Mon, 28 May 2007 00:43:03 -0700, MarkS <(E-Mail Removed)>
> wrote:
>
> >Hi,
> >I have to copy a lot of queries out of a access 97 database in to another
> >access 97 database. Their is at least one corrupt table in the database.
> >I would like to get the tables as well but can live with it if I need to
> >recreate them.
> >Yes it has to be in access 97 - very bad move
>
> Actually 97 is still the best, most stable version of Access out there.
>
> As noted elsethread, File... Get External Data... Import should work fine with
> your queries, even with a corrupt table. You can also import Forms, Reports
> and code, and the undamaged tables. Depending on *how* the table is corrupted,
> you may be able to salvage the data; one technique is to import the table,
> *design mode only*; then use File... Get External Data... Link to link to it,
> and run an Append query to append the undamaged records. You do need to use
> criteria on the table's Primary Key to select records known to be undamaged -
> if it's a corrupt Memo field then you should NOT apply any criteria to the
> memo field. Instead, identify the damaged record and use a range of ID values
> so that the damage record is not touched. For example, if you know that the
> record with ID 3155 is corrupt, use a criterion
>
> <= 3154 OR >= 3156
>
> to "touch" only undamaged records.
>
> John W. Vinson [MVP]
>

On Mon, 28 May 2007 17:10:01 -0700, MarkS <(E-Mail Removed)>
wrote:

>I didn't know the import function was in Access 97, as the IT department has
>removed it and a lot of the other functions. Have asked to get it installed,
>this removal of functions is why I am not happy with it

Well....

Don't blame Microsoft for actions of your IT department.

John W. Vinson [MVP]

Copying the data is as easy as importing from the other database.

First do the tables.
Secondly recreate the corrupted tables and update the data. see
below...
last import the queries
And Access 97 is as stable as any other, just doesn't have some
functions and is harder to edit subforms and sub reports etc.

Corrupt tables are trickier.

Often just one or a couple of records might be lost.

You need to create the table design and then run and append query and
find out where the query dies and just filter out those records.

Regards,
Tom Bizannes
Microsoft Access Development
Sydney, Australia