Regarding saving database objects as text files and importing them...

[MLH]

GHudson has working procedures posted at
http://www.access-programmers.co.uk/...ad.php?t=66320
They work. Relationships, however, and some minor default settings are
not preserved. Reestablishing some default settings and settings is a
small price to pay for a set of text files that may save your database
from total loss #AND# seem to remove the database bloat as well.

I was wondering if someone knew how to preserve the relationships
as text files so they wouldn't have to be rebuilt from scratch after
importing tables.

[David Lloyd]

One alternative, and this is something of a roundabout method, would be to
create a table for the properties of the DAO Relation object, and then loop
through each Relation in the Relations collection, saving the properties as
a record in the table. You could then export the table to text as any other
table. Upon re-importing this table, you could use this table to recreate
each relation using the CreateRelation method. If you notice, the
properties of the Relation object and parameters of the CreateRelation
method match up.

I have not tested this approach. I am merely offering it up as one approach
you may want to consider.

--
David Lloyd
MCSD .NET
http://LemingtonConsulting.com

This response is supplied "as is" without any representations or warranties.
"MLH" <CR**@NorthState.net> wrote in message
news:lc********************************@4ax.com...
GHudson has working procedures posted at
http://www.access-programmers.co.uk/...ad.php?t=66320
They work. Relationships, however, and some minor default settings are
not preserved. Reestablishing some default settings and settings is a
small price to pay for a set of text files that may save your database
from total loss #AND# seem to remove the database bloat as well.

I was wondering if someone knew how to preserve the relationships
as text files so they wouldn't have to be rebuilt from scratch after
importing tables.

[MLH]

Its definitely something I had not thought of. Others in this
NG have commented that they would like to see a 100%
database build from text. It has been suggested that such
would make for an excellent Add-In for Microsoft Access.

This much, I know - and that is, I would pay for it if it were
available. For certain.

[watto]

Have you tried exporting the MSysRelationships table and importing it
to restore the relationships? I have no idea if it will work or if it
will let you, but worth a try. Turn on View | System Objects in Options
to see the system tables.

[David W. Fenton]

"watto" <wa******@gmail.com> wrote in
news:11**********************@g44g2000cwa.googlegr oups.com:

Have you tried exporting the MSysRelationships table and importing
it to restore the relationships? I have no idea if it will work or
if it will let you, but worth a try. Turn on View | System Objects
in Options to see the system tables.

It won't work. It's owned by the DB engine, and you don't have any
permissions on it at all -- you can't replace it or delete or append
records to it. You'd just end up with a second table with a
different name that is useless.

That's the case with most of the system tables.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[lylefair]

You could try something like:
Debug.Print
CurrentProject.Connection.OpenSchema(adSchemaForei gnKeys).GetString(adClipString,
, vbTab, vbNewLine)

[lylefair]

There are many of these floating around news groups.
Of course we get an pristine, tiny as possible copy of the tables and
relationships, with
SaveAsText, 6, "", NewFilePathName
and it's quite simple to loop through the other objects and save them
as text, and to recover them as well.

I wrote and posted one of these several years ago and I believe one is
avaiable in the downloads section of my site (FFDBA.com).

The only challenge TTBOMK is the References which must be kludged a
bit.

Now it's true that the teables are not saved as text, but they are
saved without any other crud, and they are saved about as small as they
can be saved.
If this isn't good enough, and I see no reason it isn't, then using the
ADO recordset Save Procedure will do that.

I've figured out why you annoy me. It's because you base your questions
and comments on assumptions which are not true, but which you imply are
self-evident, or universally accepted. Mostly they are S__t!

[rkc]

lylefair wrote:

I've figured out why you annoy me. It's because you base your questions
and comments on assumptions which are not true, but which you imply are
self-evident, or universally accepted. Mostly they are S__t!

I figured out why you amuse me a long time ago.

[Lyle Fairfield]

rkc wrote:

lylefair wrote:

I've figured out why you annoy me. It's because you base your questions
and comments on assumptions which are not true, but which you imply are
self-evident, or universally accepted. Mostly they are S__t!

I figured out why you amuse me a long time ago.

Enjoy!

[rkc]

Lyle Fairfield wrote:

rkc wrote:

lylefair wrote:

I've figured out why you annoy me. It's because you base your questions
and comments on assumptions which are not true, but which you imply are
self-evident, or universally accepted. Mostly they are S__t!

I figured out why you amuse me a long time ago.

Enjoy!

I do.

[David W. Fenton]

"lylefair" <ly***********@aim.com> wrote in
news:11**********************@z14g2000cwz.googlegr oups.com:

There are many of these floating around news groups.
Of course we get an pristine, tiny as possible copy of the tables
and relationships, with
SaveAsText, 6, "", NewFilePathName
But that only works when run from the MDB in which the tables are
stored. Believe me, I tried to make it back up a back end MDB from
the front end, and I never could make it work.
and it's quite simple to loop through the other objects and save
them as text, and to recover them as well.

If you're unsplit, then, yes, your suggestion works. In the normal
split Access app, I've never found a way to backup the data with
SaveAsText

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[MLH]

I'm working in A97.
xxxxxxxxxxxxxxxxxxxxxxxxxx

You could try something like:
Debug.Print
CurrentProject.Connection.OpenSchema(adSchemaFore ignKeys).GetString(adClipString,
, vbTab, vbNewLine)

[MLH]

Here's an assumption that may or may not be true, but you may infer
that I'm implying it is: You infer <> I imply

I've figured out why you annoy me. It's because you base your questions
and comments on assumptions which are not true, but which you imply are
self-evident, or universally accepted. Mostly they are S__t!

[MLH]

S__t!??? What are you implying with S__t!?
Salt? Spit? Snot? What? I think I know what
you are implying but you can see its easy to infer
otherwise. I don't think I've ever stated outright
on this forum that anything is self-evident, or
universally accepted. Knowing this, maybe
my future posts won't annoy you as much. I certainly
appreciate your answers and your help when you
give it. For the most part, I ask questions when I need
the answers. Sometimes I ask about things that really
don't matter much - just out of curiousity. But most of
my questions are a means to an end that is of some
importance to me.

I've figured out why you annoy me. It's because you base your questions
and comments on assumptions which are not true, but which you imply are
self-evident, or universally accepted. Mostly they are S__t!

[aaron.kempf]

yeah.. there is a solution for that.

1) use access data projects - script out anything you need via SQL
Server.
2) visual source safe has an add-in that will export forms, reports to
txt files.

MDB is a waste of resources.