Is it possible only backup Tables!

[Bob Vance]

Is there a shortcut That you can use Only to back up tables and not
forms,Queries,Modules,reports

 

[louisjohnphillips]

Is there a shortcut That you can use Only to back up tables and not
forms,Queries,Modules,reports

If you can use vba in a code module, the DoCmd.TransferDatabase method
facilitates exports of individual tables to other tables in other
databases or to a operating system file.

 

[Pete D.]

Best way would be to split the database into frontend and backend so all you
worry about is the backend backup with all your tables.

Is there a shortcut That you can use Only to back up tables and not
forms,Queries,Modules,reports

If you can use vba in a code module, the DoCmd.TransferDatabase method
facilitates exports of individual tables to other tables in other
databases or to a operating system file.

 

[John W. Vinson]

Is there a shortcut That you can use Only to back up tables and not
forms,Queries,Modules,reports

Yes. Use the Database Splitter Wizard to split your database into a frontend
(containing forms, queries, modules and reports) and a backend (containing
only tables). Then you can back up either or both databases.

 

[Bob Vance]

John is this possible to use when you only have Microsoft Runtime?
I am trying this code but only seems to let me back up 1 Table and then when
I add a 3rd I get a error wrong amount of arguments or Invalid property
assignment
Thanks...Bob

 

[Bob Vance]

Chris is it possible to backup a back end if you only have Microsoft Runtime
version on your machine.............Thanks Bob

 

[John W. Vinson]

John is this possible to use when you only have Microsoft Runtime?

Unfortunately, I don't believe so. Do you have access to any machine with the
full version? I think you'll need to split the database using retail Access,
and you'll then be able to use it with the runtime.

If the data isn't confidential, contact me offline - it would be quick and
easy to split it for you.

 

[Bob Vance]

Thanks John I have MA 2007 but my friens would only have runtime so if my db
(accdb) is split can they just back up the tables from backend from
runtime....Regards Bob

 

[John W. Vinson]

Thanks John I have MA 2007 but my friens would only have runtime so if my db
(accdb) is split can they just back up the tables from backend from
runtime....Regards Bob

Ah!

They would NOT need to split the database. You would split the database, and
give them copies of the frontend and backend.

They can back up the backend (the .mdb or .accdb file containing the tables)
outside of Access, just using Windows Explorer; or if you prefer, using the
File... Backup feature within Access (though that can be rather clunky I
understand).

They would NOT need the retail version to do this.

 

[Bob Vance]

Thanks for your help John, I will go have a read up about splitting my db,
any there any advantages to splitting, and does that mean you have to dbs in
a folder?..Regards Bob

 

[John W. Vinson]

Thanks for your help John, I will go have a read up about splitting my db,
any there any advantages to splitting, and does that mean you have to dbs in
a folder?..Regards Bob

Yes, there are advantages to splitting - I'd say more and call it ABSOLUTELY
ESSENTIAL.

And yes, you must put your database in a folder - since every file on Windows
must be in a folder, including all your database files, I'm not even sure what
you're asking. Are these users all working with their own independent
databases, or are all the users sharing the same data?

http://www.granite.ab.ca/access/splitapp

has Tony Toews' excellent discussion of the subject.

 

[Bob Vance]

Tahnks John they will be using full versions of my database with there own
data , Im thinking of putting KeyedAccess added to it so they cant copy it
to there friends , Regards Bob

 

[Allen Browne]

The advice you have received on splitting is well worth the effort, Bob. If
it's something you want to read further on, here's an introductory article:
http://allenbrowne.com/ser-01.html

Backing up an Access database while it is in use is not a simple task. There
are various locking strategies that could be in use, and with multiple
users, the data may actually change while it is being backed up, in which
case you have an inconsistent copy.

But if you think it may be worth trying to get a snapshot of the data
anyway, here's some code that is not a complete utility, but does create a
copy of whatever data it can get at, in whatever state it's currently in, to
get a potentially incomplete snapshot of the data only at a point in time:
http://allenbrowne.com/unlinked/backup.txt

 

[a a r o n . k e m p f]

splitting is not reccomended.

Splitting is depecrated.
single connection to sql server- where all data SHOUD belong is a much
much simpler architecture.

FILE, NEW, Project (Existing Data)

anything else is a waste of time

 

[Bob Vance]

aaron crap I dont want anything to do with their data only my program...get
real

message
splitting is not reccomended.

Splitting is depecrated.
single connection to sql server- where all data SHOUD belong is a much
much simpler architecture.

FILE, NEW, Project (Existing Data)

anything else is a waste of time

 

[Fred]

In case you don't already have the decoder ring, Aaron answer all Access
questions with "don't use Access" and thus his answers to these are never
really answers.

 

[Bob Vance]

Thanks Allen , But this DB is stand alone, and only one user can use one db
they are not linked together, each person has their own Db...........Regards
Bob

The advice you have received on splitting is well worth the effort, Bob.
If it's something you want to read further on, here's an introductory
article:
http://allenbrowne.com/ser-01.html

Backing up an Access database while it is in use is not a simple task.
There are various locking strategies that could be in use, and with
multiple users, the data may actually change while it is being backed up,
in which case you have an inconsistent copy.

But if you think it may be worth trying to get a snapshot of the data
anyway, here's some code that is not a complete utility, but does create a
copy of whatever data it can get at, in whatever state it's currently in,
to get a potentially incomplete snapshot of the data only at a point in
time:
http://allenbrowne.com/unlinked/backup.txt

 

[David W. Fenton]

Yes. Use the Database Splitter Wizard to split your database into
a frontend (containing forms, queries, modules and reports) and a
backend (containing only tables). Then you can back up either or
both databases.

And if you want a valid warm backup of the back end, open it and
type this in the immediate window:

Application.SaveAsText 6, vbNullString, [path/filename of new MDB]

That will create a new MDB with all the tables in it, and do it via
Jet so that all record locking will be honored (i.e., so you can't
get an inconsistent state of data, such as you can if you try to
copy an open MDB through the file system).

I have yet to find a way to run this code from another MDB, though.
It seems to work only on the CurrentDB, and even opening the back
end in another instance of Access doesn't work for some reason. I
don't know why.

Lyle? Are you listening?

 

[David W. Fenton]

there are advantages to splitting - I'd say more and call it
ABSOLUTELY ESSENTIAL.

Every Access application with more than one user should be split. NO
EXCEPTIONS.

Every Access application where the user needs to get updates to the
forms/reports from someone else should be split, even if it has only
one user. NO EXCEPTIONS.

Every replicated Access app should be split. NO EXCEPTIONS.

 

[David W. Fenton]

There's no button on a toolbar or menu choice, if that's what
you're looking for. But it's possible to back up a back end even
if you don't have the runtime. At the command console, type:

copy C:\db.mdb C:\backup\db.mdb

Backing up through the file system is not necessarily going to
produce a valid backup copy, since the disk image could be in an
inconsistent state. The only valid backup would be through Jet.