Discuss "Help with handling sql insert error" in the ASP Development forum.

1 - Have the same problem right now. It kind of depends on if the old table is still being updated or used by other applications. The best solution would be to retire the old table and put it's data into the new format; tho I fully realize that it may not be possible if other system rely on its format. Consider creating a VIEW that UNIONs the two tables together.

2 - I really don't see much issue using the Equipment Number as the PK since it's a single field and is unique -- you're probably going to create a Unique Index on it anyway.

3 - Same answer as #1 -- create a VIEW that makes the old format look like the new one and UNION ALL the tables together.

__________________
Wolffy
------------------------
Opinions expressed are my own and do not necessity reflect those of any sane person. Any code provided is intended to be an example and is provided AS IS. Rework for your specific environment may be required. Void where prohibited by law. Not valid in California. Your mileage may vary.

on # 1 - cool...thanks for the advice...i think i would rather retire the old table and move that data to the new....i'll look at the data to check if thats a good possibility. then that would take care of #3.

on #2 - won't I need an autonumber ID to lock the recordset? or can i still do that off the equipment # since it can be the primary key?

Thanks!