Need help export data

  • Thread starter Thread starter dpinson
  • Start date Start date
D

dpinson

I have a customers table that I want to export to Excel. Each time I try I
get a messge that another user and me are trying to modify the same data at
the same time. I am not on a network.

Any suggestions as to what this could be.

Thanks in advance
 
dpinson,
is the customers table open when you are trying to export it?
If you are exporting from the database window, just select the table without
opening it and try to export it.


Jeanette Cunningham -- Melbourne Victoria Australia
 
I have tried both ways. Basically I have a split database with two tables,
customers and jobs. They are related via the customer ID in a one to many
relationship. I have needed to add fields to the jobs table and did so using
the .mdb database that is linked to the .be

I have about 4600 records in the old tables and am looking for the best way
to get the data from the old tables, both customers and jobs, to the new
tables. The jobs table has an autonumber field setup to increment job
numbers and a couple of required fields.

Thanks for considering my problem.
 
David,
the extra info in this post seems to be for a different problem from your
first question.
To best help us to help you, please answer:

- are the old tables and the new tables both in access?
- is this for your own database, or do you need to do this for several
customers who have the old tables in their copy of the database?
- was using excel just a way to get the data from the old tables to the new
tables?
- what is different between the new jobs table and the old jobs table?


Jeanette Cunningham -- Melbourne Victoria Australia
 
Jeanette,

Sorry for the confusion. Both tables are in the same Access database. The
database is an order entry/job ticket application and several people access
it from their server. I have the files, both mdb and .be, on a thumb drive
so I can work on them at home. They are continuing to create records in
their copy of the original database while I am adding fields, mostly boolean
and text, to the jobs table in the copy I made of the database. Excel was
just a way I thought I could get the data from their tables into the tables I
have. This would be done at their office at the end of the day so the data
transfered to the new tables is up to date. Seems like this should be
relatively easy, but I seem to have some confusion as to the best way to
approach it. All that is lacking is getting their data into the new tables.
I am not sure how to handle the only relationship I built which is between
customers and jobs with customerID as the common field. Also, the jobs table
has an autonumber field to increment job tickets and a few required fields.
The values in a combo box were changed in the new table also as they had some
new customer service reps join the firm.

Thanks for helping with this problem.

David
 
David,
it seems to me that the easiest approach is to get access to the backend on
the server at the end of the day when no one else has the database open.
Create a backup of the backend for safety before you add the extra new
fields to the table.
You already know what fields you want to add, their data types, field sizes
and any validation rules - it will be a quick process.

Adding extra customer service reps to the table for customer service reps is
something you can do from the front end.
The new customer service reps will automatically go into the customer table
in the backend and will be there for everyone to use.

You will be changing the front end to add the extra fields to the forms,
queries and reports. Just give each user a new copy of the new front end.


Jeanette Cunningham -- Melbourne Victoria Australia
 
Jeanette,

Thanks for the response. I have already changed the queries, forms, reports
on the .mdb on my end. If I re-create the new fields on their backend .be
database, will my frontend connect seamlessly to their .be database such that
I can just use the table manager to relink the tables?
 
David,
in the front end where the linked tables are, access stores the path to each
table.
Unless you have some code that checks the links to each table and verifies
each field by name each time a user opens a front end,
there shouldn't be any problem with linking to the backend.
I have never had problems relinking after a change to some fields in a table
in the backend.


Jeanette Cunningham -- Melbourne Victoria Australia
 
David,

As Jeanette has said, to update your users with a new version of the
FE file you just give them a copy of the new version which will
replace their current version. You will, however, probably need to
re-link the FE to the tables in the BE. You can do this automatically
with some VBA code, see this site for some code :-
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE_ReLink.mdb'

If you are still developing the database (as it seems you are) you
will probably want to add new fields, tables, relationships, etc to
the BE file. You can do this automatically from code in the FE by
using the code at :-
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE Update Utility.mdb'

HTH

Peter Hibbs.
 
Thanks Jeanette,

I will just add the new fields to the customer .be file and relink the
frontend to that set of tables. I still wonder though the best way to move
data from one table to another.
 
Back
Top