Access 2010 - table with same fileds and rows

[dkatorza]

Hello evryone,


need your kind help with the below,

i'm using Access 2010 and i created a main form , from which i want to let users to open new table with fixed fileds and rows, also the name of the table will be as per user choice.

so if a user want to open new table from the main menu, he will have the choice to press on a command button and a dialoge box will ask to name the table.
the new table will then be open with the same fileds and rows names( name only) .
the new table will be edited using a form.



hope i'm clear.

many thanks.

[rpeare]

You're not clear and I'm not sure you're using the correct verbiage.

Are you saying you want to give your users the ability to create a TABLE on the fly? and they can do their own data entry on that same table? This is an incredibly bad idea and poor programming primarily because you do NOT want to give your users access to change the table design/structure. Not to mention it becomes impossible to maintain relationships and ensure proper normalization of tables

a TABLE just stores data, nothing else, no calculated values, nothing
a FORM is user interface
a QUERY is a subset of data you find in your TABLE(S)

[dkatorza]

Dear rpeare,
sorry , English is not my mother tongue language.

i have a main form,
from this main form i want to let users to update prices/rates.

but also to let the the option to add companies update the rates for them.

we are working with sevral companies that givs us rates and sometimes we need to add companies.

all this details must go to diferent tables no?

if i have 6 companies and each one have diferent rates than i need table for each one.

the filds names will always be the same and rows names.

[rpeare]

You would need a table for your customers that contained a primary key (autonumber will work) for instance:

tblCustomers
CustID CustomerName ----> other fields related to customers
1      Company A
2      Company B

I do not know the structure of your pricing/rates but I'm guessing you have different rates for different items so you would likely want a 'item' table that also had an autonumber primary key and then a 'customer item charge' table that would contain the CustID, the ItemID and have it's own autonumber field as it's primary key with a field for the cost for that item for that customer.