Update Table

  • Thread starter Thread starter Rob
  • Start date Start date
R

Rob

Hi,

Using Access 2000. I have a fairly simple database which is updated with
data weekly through an import routine, however, one table in the database
needs to be updated with some new records which isn't included in the weekly
update. I could speak to the 6 other users which all use a copy of the
database to talk them through the changes needed but they aren't very
experienced with 'behind the scene' workings.

My ideal would be to export my table that I update and have them import the
table into their database and thus, overwrite their original table. I
looked at sending them the whole database less the data but they can and
have created their own queries which would be lost.

Is there a way to copy and replace a table in another database?

Thank you, Rob
 
Rob

I'm not clear on your design, based on your description.

It sounds like you have yourself and 6 users, all of whom have their own
copies of a single database.

Any chance all of you are on the same Local Area Network? If so, look into
using a "split" design, rather than independent copies of the db. Post back
here if "split" is unfamiliar...

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.
 
Jeff,

We're not on a network but standalone computers and spread across the
country so difficult to get everyone together.

I've searched for info on copying a table but nothing seems to be
straightforward.

Ta, Rob
 
Hi Rob,

1. If your table contains one or more relationships, go to Step 2. If not
go to Step 3.
2. Open the relationship window and delete all relationships in your
table.
3. Create a new database.
4. Open the new database and use File-Get External Data-Import to import
your table.
5. Send an email to the other users and attach the new database.


For the other users .........
1. Save the attached new database in the email from you.
2. Open their database.
3. If their table contains one or more relationships, go to Step 4. If
not go to Step 5.
4. Open the relationship window and delete all relationships in their
table.
5. Use File-Get External Data-Import to import the table in the database
you sent them
6. If their table contains one or more relationships, go to Step 7. If
not Close everything; they're done.
7. Recreate the relationships in the new table.

Steve
(e-mail address removed)
 
Rob

OK, not connected...

If your users are smart enough to click a button, one approach might be to
"package" your import routine and add a button to your application's main
menu or some other relevant form.

That way, your users would only need to:

* replace their copy of the form with your copy
* click the button to refresh/update

Good luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.
 
Rob,

If you get this to work for you manually, I could automate it for you so you
click a button on your end and then your users click a button on their end.
I provide fee-based help with Access applications. There would be a small
fee to automate this for you. Contact me if you want it automated.

Steve
(e-mail address removed)
 
Steve said:
Rob,

If you get this to work for you manually, I could automate it for you so
you click a button on your end and then your users click a button on their
end. I provide fee-based help with Access applications. There would be a
small fee to automate this for you. Contact me if you want it automated.

Steve
(e-mail address removed)


Stevie, if you were any good, you would have repeat customers that would
keep you busy. Pimping your services in a free support venue also shows that
you have no ethics and are definitely not someone to trust.



Stevie is our own personal pet troll who is the only one who does not
understand the concept of FREE peer to peer support!
He offers questionable results at unreasonable prices.

These newsgroups are provided by Microsoft for FREE peer to peer support.
There are many highly qualified individuals who gladly help for free. Stevie
is not one of them, but he is the only one who just does not get the idea of
"FREE" support. He offers questionable results at unreasonable prices. If he
was any good, the "thousands" of people he claims to have helped would be
flooding him with work, but there appears to be a continuous drought and he
needs to constantly grovel for work.

Please do not feed the trolls.

John... Visio MVP
 
See where Steve says to rename a file from .mdb to .dbf to make it a dBase
III file.

Subject: Re: Export an Access Table as an dbase III file 5/6/2010 1:55 PM
PST

By: Steve
In: microsoft.public.access



Hello Bill,

Try exporting your file with a .mdb extension then renaming the file to a
...dbf file. Put the following code after your DiCmd.TransferDatabase command:

Dim OldName, NewName
OldName = "K:\CPANALYSIS\BusinessMgt\VP\Access\DBASE\tbs1.mdb"
NewName = "K:\CPANALYSIS\BusinessMgt\VP\Access\DBASE\tbs1.dbf"
Name OldName As NewName

Steve
(e-mail address removed)

http://www.microsoft.com/communitie...3c3-c10e-4523-9213-cdfd537838f1&lang=en&cr=US
 
You are an ignoramus, Karl. You think you know it all and that gives you the
right to act as an ignoramus.

Look at the microsoft.public.access OP's post again. His file is being
exported as a DBase III file. My suggestion merely says to save it with a
..mdb extension and then change the extension to .dbf.

You ought to be nominated for MVP Visio and then you would be as ignorant as
visio john.

Steve
 
Back
Top