Move data from one table to the other via yes/no boxes?

Altecice

New member
Local time
Today, 20:49
Joined
Jul 2, 2013
Messages
2
hey there,
I cant figure this one out for myself so any help would be awesome, I have two tables;

Parts
Sold Parts

now what i am trying to get to happen is using a YES/NO box, Say i have a "part" in the parts table when i click the YES/NO box, to have the tick to say it has been sold, I want that line to move to the Sold Parts table. is this even possible?

(if you can suggest a better way to do this that would help!)
 
I'd leave the data in one table. The Yes/No field tells you whether the part has been sold or not. If you really want to do it, you'd use an append query and a delete query, each using that field as a criteria.
 
Possible. Possible but, certainly, NOT necessary.
I understand that Parts and SoldParts have exactly the same structure (as fields)
So, forget the SoldParts table, (delete it).
In the Parts table add a new field Sold of type Yes/No.

Create a form based on this table (use the Form Wizard).
For the Sold field you will see check boxes control(s).
Check the part(s) that are "sold".
That is all to do in order to have Parts (not sold) and Parts(sold)

Now, if you wish to show all the parts, the parts(not sold), the parts(sold) you must define queries. A little bit more advanced programmer skill will allow you to design a single parametric query for all this situations.
 
Like everyone here, i suggest also not to use a separate table. If you insist on doing so, you will have to take in the consideration the possibility to move records from sold parts to (unsold) parts also. Too much unnecesary work.
 
A single table is the best option but, eventually, you will want to purge old data so think about it and decide how many years worth of history you want to keep active. At least one full year plus the current year is recommended. So, you ultimately end up with 25 months worth of data. That way you can do year over year reporting as well as month over month.

Rather than using a y/n field which provides very little information, I would use a SoldDate field. That would provide useful information for reporting on sales activity. SoldBy is also a possibility if you might want to pay commissions.
 

Users who are viewing this thread

Back
Top Bottom