unrelated tables

[Per]

Hi,

I've enherited a database with two tables containing unrelated
keys (1 goes from 100-300, the other from 500-1000). The folks
doing data entry like the seperate tables so I can't combine
them (they use them like excel files).

I need to create a form for adding today's date to a record in
one or the other table, depending on what's entered. So, if one
entered "150" it would store the date in the table with ids from
100-300. If one entered "700", it would store the date in the
other table.

I've thought about having a table to take the entered ids and
the the date, and linking it to the other tables, but because the
other tables are not related, this is not possible.

I've thought about using VBA (maybe runSQL or ?) to update the
proper table when new data is entered on the form, but I'm curious
if this is the best way to do it. If so, is runSQL what I want
to use (I need accuracy and relative speed in updating the tables
since the method of data entry will be a barcode scanner, rapidly
scanning in ID codes)?

Any advice would be gladly appreciated!
Per

 

[Jeff Boyce]

Per

Access is a relational database. Excel is a spreadsheet. If your folks
prefer a spreadsheet, what do you gain from giving them Access tables?

 

[cb]

I didn't, the person who developed
the database did. I'm trying to help
them out by giving them a form that
will allow them to scan barcodes into
their database. All I need it to do
is find the correct record, in the
correct table, and insert date() in one
of the columns.

If I were the person designing the
system, I'd still use access, but I'd
set it up better (one table with all
the id codes).

Thanks again,
Per

 

[Jeff Boyce]

Per

Any reason you can't (re-)build it correctly? Do the users have to know
they have only one table instead of two?