New to VB, not sure where to start

[vidus]

Hello, I am new to VB but would like to take advatage of it for our access tables. Heres what I want to do.

We have a datasheet with potential jobs from customers, on the datasheet we have a combobox with "yes" and "?" for that record. When we get the job we select "yes".

We also have a seperate datasheet for current jobs. What I want to do is have it set so that when you select "yes" on the first datasheet, it will automatically move that record (or parts of it) to a new record on our current jobs datasheet. That way we dont have to do this manually...

Is this something that VB is used for? If so.. where do I even start?
Cheers!

 

[ajetrumpet]

this is hard to explain, but the first thing I would say here is that you are treating Access like Excel, which is OK, but it won't work in the long run. I think what you really should have here is one table with all jobs in it, and one field that indicates weather you are working on it or not. The setup right now I think is redundant. If there is one table, then you will know just by one field what you are working on, and what is still pending through negotiations. If you have to leave it the way you have it though, you will either have to use a recordset object in VB language, or an update query, with references to your old table.

 

[vidus]

this is hard to explain, but the first thing I would say here is that you are treating Access like Excel, which is OK, but it won't work in the long run. I think what you really should have here is one table with all jobs in it, and one field that indicates weather you are working on it or not. The setup right now I think is redundant. If there is one table, then you will know just by one field what you are working on, and what is still pending through negotiations. If you have to leave it the way you have it though, you will either have to use a recordset object in VB language, or an update query, with references to your old table.

Yes I realize this.. but the reason we have 2 seperate tables, is because once we get the job, we need to record a totally different set of data, its just way easier to use for us to have current jobs in a seperate table and have potential jobs in another because of the variation in data.

Ill do some searching on recordset.