General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
I think Jim's approach is the best for a lot of reasons. You can ask for transaction type before the screen is called and when it's called, its labels and controls reflect the chosen type of transaction but the underlying design is still one table and one form making the code and the data more maintainable.
In short, your GUI should eliminate that concern you had.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only