I have an account details form that contains account numbers (more than one) and Customer name, dates, etc; The account numbers may have the same customer so iwould like to have title "same data to all accounts?" and tick box next to it. Upon clicking this the user the user does not have to make individual entries for the same customers, for eg typing in the account numbers and same customer everytime. Plz HELP
a tick button question?
- Thread starter Choksy
- Start date
Mile-O
Back once again...
- Local time
- Today, 20:49
- Joined
- Dec 10, 2002
- Messages
- 11,316
I've read your other posts and it sounds as if you really do not know what you are doing.
Before you even begin to ponder forms, queries, etc you will have to understand the process that you are intending to simulate. This means going right down to the bottom - the tables. You are goingto have to understand the basic database principles of normalisation otherwise you are going to be posting questions left, right, and centre on this forum.
We are, after all, not paid to give advice, offer solutions, etc - its just nice to share one's knowledge when time is available.
You are, however, expected to be willing to do the majority of the groundwork (and the rest of the work) - not expect people to build your design step by step when it seems so obvious that you haven't even thought it through enough. If you keep going this way you'll get to a point, get stuck, regress, and ask a question that'll send you off in another direction.
So, for your own benefit, you should read - and understand - this, and download the Word document called Understanding Relational Database Design from here. Also, for further information you don't even have to ask - the forum has a search function in the top right of the site where, the chances are, someone will have asked questions similar to yours, all you have to do is Search.
If you know what you are doing then by all means be specific but detail exactly what you mean - don't write on here as if sending a text message, it's horrible to read. If you don't know what you are doing or what you want then don't be so specific - think general, take a step back, and have a good hard think about what you really want.
Before you even begin to ponder forms, queries, etc you will have to understand the process that you are intending to simulate. This means going right down to the bottom - the tables. You are goingto have to understand the basic database principles of normalisation otherwise you are going to be posting questions left, right, and centre on this forum.
We are, after all, not paid to give advice, offer solutions, etc - its just nice to share one's knowledge when time is available.
You are, however, expected to be willing to do the majority of the groundwork (and the rest of the work) - not expect people to build your design step by step when it seems so obvious that you haven't even thought it through enough. If you keep going this way you'll get to a point, get stuck, regress, and ask a question that'll send you off in another direction.
So, for your own benefit, you should read - and understand - this, and download the Word document called Understanding Relational Database Design from here. Also, for further information you don't even have to ask - the forum has a search function in the top right of the site where, the chances are, someone will have asked questions similar to yours, all you have to do is Search.
If you know what you are doing then by all means be specific but detail exactly what you mean - don't write on here as if sending a text message, it's horrible to read. If you don't know what you are doing or what you want then don't be so specific - think general, take a step back, and have a good hard think about what you really want.
