KenHigg
Registered User
- Local time
- Today, 12:20
- Joined
- Jun 9, 2004
- Messages
- 13,327
Mike,
In response to your post where you suggested the user make a separate table for each customer: Can you fathom a db where you never have to worry about creating new tables, etc. Where all you do is enter data on forms. That is the essence of the db's that the senior posters in this forum strive to create. And the reason is so that an end user does not have to have a clue as to what a query or macro is. They simply put in data, push a button, and presto, their data comes out and then they can focus on running their business and not having to read Access instruction manuals. They say "Give me a form to do my inputs and button to get my reports - I do not even care that you may be using Access to create it!"
Now that is not to say that a db where you continuously add tables, etc., through out the life of the db is not a useful tool. You have proven other wise. It's just that some of the solutions you propose can lead to a situation where the end user will have to be an Access person to use. See the problem?
Eventually, a db like the one you have gets to the point where redesigning it is hopeless but your business can not run with out it. Now, everything is still cool because you're there to baby it, but I would suspect that when you go to show your potential new business owner how to run it, you're going to be hosed and it will be a liability that few new potential business owners will want to deal with...
Having said all that - can you see why the senior posters here sometimes get upset with your advice?
Can we still be friends?
Ken
In response to your post where you suggested the user make a separate table for each customer: Can you fathom a db where you never have to worry about creating new tables, etc. Where all you do is enter data on forms. That is the essence of the db's that the senior posters in this forum strive to create. And the reason is so that an end user does not have to have a clue as to what a query or macro is. They simply put in data, push a button, and presto, their data comes out and then they can focus on running their business and not having to read Access instruction manuals. They say "Give me a form to do my inputs and button to get my reports - I do not even care that you may be using Access to create it!"
Now that is not to say that a db where you continuously add tables, etc., through out the life of the db is not a useful tool. You have proven other wise. It's just that some of the solutions you propose can lead to a situation where the end user will have to be an Access person to use. See the problem?
Eventually, a db like the one you have gets to the point where redesigning it is hopeless but your business can not run with out it. Now, everything is still cool because you're there to baby it, but I would suspect that when you go to show your potential new business owner how to run it, you're going to be hosed and it will be a liability that few new potential business owners will want to deal with...
Having said all that - can you see why the senior posters here sometimes get upset with your advice?
Can we still be friends?
Ken