Hi Guys,
I could do with a little help in sorting the correct design for a database i have to build. I'm in a bit of a rush with it, and only have a few days to get it all sorted, so all information would help.
I need to create, what we will term, an ORDER COUNT.
Basically, batched orders come into our department and we have to record the amount in the batch, where they have come from, the "method" (post, tel, web, fax, email, online, import) and whether they are "non public" or "public", the "status". In addition to this, there is currently around 30 different clients that I will have to collect this data for.
What I thought, and i know it is not "normal" is to have a separate table for each client that would record this data (there are many reasons for this, exporting & reports ease as well as the ability to add in new clients and remove old clients). Ontop of this i would have the client listing.
What i'm a little stuck on is the form and how that is going to be designed - i'm thinking for ease of use to have a main section where you click the client, then a subform opens which sets the recordset of the subform to the client selected and will then therefore throw the data into the correct table - im not sure if this is possible, so any advice please feel free.
Also, i'm thinking about the reporting of it. Baring in mind that I will be requiring a lot of stats pulled from the data, would this be better off done in some like crystal reports, as opposed to within access.
as i said before, any advice, examples, help would be an enormous help right about now, as im slightly worried about the very short amount of time ive got.
Thanks
I could do with a little help in sorting the correct design for a database i have to build. I'm in a bit of a rush with it, and only have a few days to get it all sorted, so all information would help.
I need to create, what we will term, an ORDER COUNT.
Basically, batched orders come into our department and we have to record the amount in the batch, where they have come from, the "method" (post, tel, web, fax, email, online, import) and whether they are "non public" or "public", the "status". In addition to this, there is currently around 30 different clients that I will have to collect this data for.
What I thought, and i know it is not "normal" is to have a separate table for each client that would record this data (there are many reasons for this, exporting & reports ease as well as the ability to add in new clients and remove old clients). Ontop of this i would have the client listing.
What i'm a little stuck on is the form and how that is going to be designed - i'm thinking for ease of use to have a main section where you click the client, then a subform opens which sets the recordset of the subform to the client selected and will then therefore throw the data into the correct table - im not sure if this is possible, so any advice please feel free.
Also, i'm thinking about the reporting of it. Baring in mind that I will be requiring a lot of stats pulled from the data, would this be better off done in some like crystal reports, as opposed to within access.
as i said before, any advice, examples, help would be an enormous help right about now, as im slightly worried about the very short amount of time ive got.
Thanks
