E
Edward Letendre
Okay, I have a few more questions for the experts here.
This is my basic understanding of the situation as it stands now. I am
working with a database that I did not setup myself. The current situation
is as follows:
1. When the main form is opened up, the user can select what year of data
he or she wants to access and from that point, the user can enter new data or
just access old records from the past (the data in this database ranges from
1995 to 2005). The table that the user wants to connect to is selected by a
radio button corresponding to the choice (1995, 1996, 1997, etc.). I want to
change the choices to a drop down menu that displays all current tables and
future tables in the drop down menu (including the 2006 tables and the 2007
tables when I get to those years). Where would I code or add the new years
to the drop down list (I was thinking of having the info loaded from a table
with just year values, unless someone else can come up with something that
would include the adding of the current date or current year to the drop down
list.
2. When a user opens an older table (such as the 1995 table), the
programmer wanted to make sure that the user could not enter new data or
incorrect data into the older table (such as entering 2005 data into the 1995
table and such). This process is handled with a case statement in code and
such. What I want to know is how can I by pass the need for the case
statement and have the form put data in the correct table from the form
screen.
3. Something not relating to the form but I want to ask here as it is also
a part of my situation is as follows: When the new year rolls around, the
user data must be stored in a new table based on the year. In my case, the
customer information is stored in a table called ATS_CUSTOMER_1995 table.
The new customer information would then be added to new tables based on the
year. The company I work for, also stores the products that are sold or
created for each customer. Thus a product table is created for each year,
again called ATS_PRODUCT_1995 table. Each of these tables have been created
for each year that the database was in use (1995 to 2005). In the future,
new tables will have to be created. Is there a way to automate this process
so that in the future say around January 1, 2006 say, the tables are then
created with the year in their name (such as ATS_CUSTOMER_2006 and
ATS_PRODUCT_2006 and so on as the database gets used into the future?
Edward Letendre.
This is my basic understanding of the situation as it stands now. I am
working with a database that I did not setup myself. The current situation
is as follows:
1. When the main form is opened up, the user can select what year of data
he or she wants to access and from that point, the user can enter new data or
just access old records from the past (the data in this database ranges from
1995 to 2005). The table that the user wants to connect to is selected by a
radio button corresponding to the choice (1995, 1996, 1997, etc.). I want to
change the choices to a drop down menu that displays all current tables and
future tables in the drop down menu (including the 2006 tables and the 2007
tables when I get to those years). Where would I code or add the new years
to the drop down list (I was thinking of having the info loaded from a table
with just year values, unless someone else can come up with something that
would include the adding of the current date or current year to the drop down
list.
2. When a user opens an older table (such as the 1995 table), the
programmer wanted to make sure that the user could not enter new data or
incorrect data into the older table (such as entering 2005 data into the 1995
table and such). This process is handled with a case statement in code and
such. What I want to know is how can I by pass the need for the case
statement and have the form put data in the correct table from the form
screen.
3. Something not relating to the form but I want to ask here as it is also
a part of my situation is as follows: When the new year rolls around, the
user data must be stored in a new table based on the year. In my case, the
customer information is stored in a table called ATS_CUSTOMER_1995 table.
The new customer information would then be added to new tables based on the
year. The company I work for, also stores the products that are sold or
created for each customer. Thus a product table is created for each year,
again called ATS_PRODUCT_1995 table. Each of these tables have been created
for each year that the database was in use (1995 to 2005). In the future,
new tables will have to be created. Is there a way to automate this process
so that in the future say around January 1, 2006 say, the tables are then
created with the year in their name (such as ATS_CUSTOMER_2006 and
ATS_PRODUCT_2006 and so on as the database gets used into the future?
Edward Letendre.