Re: Move record from one table to another
- From: "ManningFan" <manningfan@xxxxxxxxx>
- Date: 26 Jul 2006 12:37:36 -0700
A better question is; Why? Why move a record from one table to
another? If you're trying to differentiate between one type of record
and another, why not just add a flag to the table?
What you're asking for is fairly easy to do, but moving records from
table to table isn't a very logical or stable way to track data.
I think rather than ask someone help you commit suicide, you should ask
someone for some guidance. Building a database isn't like building
with Legos, not everyone fully understands the concepts needed to build
a database properly. If they did, true DBAs wouldn't be making
$80K/yr.
Joshua.Buss@xxxxxxxxx wrote:
I am trying to move a record from one linked table to another within
access, but I'm a complete beginner to VBA and don't know exactly where
to begin.
I have an access file that has the two linked tables, which each link
to separate SQL databases using separate ODBC connections.
I have a form that has a view of table1 and a set of buttons for
manipulating the data in database1.
The tough part is the button that's going to go on this form which
moves the record that's currently being viewed into a new record in
table2 (database2).
Through extensive testing I thought I found it's impossible to simply
do this with the built-in form builder tools - it only works if one of
the tables are local and not linked. However, queries which manipulate
data between linked tables work fine, which is what gave me the notion
I could do this with a little VBA code and a couple custom queries.
So far, the plan is the make the button do this:
1) Set a "pushFlag" column in the record in table1 to a specific
identifying value ("1" for now)
2) Runs an insert query to insert "all records with pushFlag = 1"
into table2. (this would create a copy of the record)
3) Sets the "status" field in the new record in table2 to a specific
value. ("done" for now)
4) Runs a delete query that first checks for duplicates (records that
exist in both the table1 and table2) and if a duplicate is found the
table1 record is removed. If a duplicate is not found, then the insert
must have failed for some reason. Instead of deleting the record the
user is notified that the insert failed, probably because of mal-formed
data in the record.
Does this sound remotely feasible? Would anyone be willing to help me
get this to work?
.
- Follow-Ups:
- Re: Move record from one table to another
- From: Joshua . Buss
- Re: Move record from one table to another
- References:
- Move record from one table to another
- From: Joshua . Buss
- Move record from one table to another
- Prev by Date: Problem with record addition in subform
- Next by Date: Re: Problem with record addition in subform
- Previous by thread: Move record from one table to another
- Next by thread: Re: Move record from one table to another
- Index(es):
Relevant Pages
|