E
Edward Letendre
Hello, My name is Edward Letendre. I have been asking questions to this
group about an access database application that was written in Access 2.0 but
is being converted to access 97 and will become a split database.
Anyways, I am testing the split part of the database. The split database
seems to be functioning okay. What I need to know is how will my code be
effected by the splitting of the database. Are there any changes that need
to be made to the code as there is quite a lot of use of case statements in
accessing tables such as the following code:
case 2000: table_name = 'ATS JOBS 2000'
case 2001: table_name = 'ATS JOBS 2001'
etc.
another concern I have is with the year code that is used alot in this
particular application. By choice of the programmer, the year is set as
follows:
cur_year as integer (for the variable to be used in this example)
cur_year = 2005
Thus by setting the cur_year integer to 2005, and when the date changes to
2006 and so on, the code has to be changed to cur_year = 2006, cur_year=2005
and so on and so on. I want to manually set the year using code something
like this:
cur_year as integer
cur_year = year(date())
Thus with the year() function and the date() function, I hope to see the
year 2005 for the next few weeks and then the year 2006 and beyond as the
program continues to get used.
Something really confusing happned to me today as well wiht the code I am
seeing in this application. Within a user developed procedure, I have seen a
case statement such as the following:
Select Case EditYearVal
Case 95: jobtabname = 'ATS JOBS 1995'
linetabname = 'ATS LINES 1995'
Case 96 jobtabname = 'ATS JOBS 1996'
linetabname = 'ATS LINES 1995'
...
Case 2004 jobtabname = 'ATS JOBS 2004'
linetabname = 'ATS LINES 2004'
Case 2005 jobtabname = 'ATS JOBS 2005'
linetabname = 'ATS LINES 2005'
in my case, the case statment was as shown above with all the values from
1995 to 2005 (I just typed a few to show you what it looks like here). This
afternoon, I opened the code and did a database conversion from access 2.0 to
access 97 and then I split the database into a front end and a back end.
Both processes were successfully complted, but when I just checked the code
in the procedures or modules if you like, I saw a new case statement added to
this case statement and it was as follows:
Case 2006: jobtabname = 'ATS JOBS 2006'
linetabname = 'ATS LINES 2006'
note to this new case statement, I did not create any new tables for 2006
and no other case statements have been updated to this point. How in the
world could have this new case statement be added to the modules. If this
was possible, why was the code no modified to update itself else where.
What I need to know is how can I identify where the update takes place and
what I can do to stop it, as I would like to simply have all the use of the
case statement to be like the following:
Select case yearval
case 95: jobtabname = 'ATS JOBS 1995'
...
Case Else: jobtabname 'ATS JOBS AFTER 2005'
thus the case else would be used as a catch all to have all new values used
beyond the year 2005, inwhich this database is very year based.
I hope this makes sense and someone here can help me.
Edward Letendre.
group about an access database application that was written in Access 2.0 but
is being converted to access 97 and will become a split database.
Anyways, I am testing the split part of the database. The split database
seems to be functioning okay. What I need to know is how will my code be
effected by the splitting of the database. Are there any changes that need
to be made to the code as there is quite a lot of use of case statements in
accessing tables such as the following code:
case 2000: table_name = 'ATS JOBS 2000'
case 2001: table_name = 'ATS JOBS 2001'
etc.
another concern I have is with the year code that is used alot in this
particular application. By choice of the programmer, the year is set as
follows:
cur_year as integer (for the variable to be used in this example)
cur_year = 2005
Thus by setting the cur_year integer to 2005, and when the date changes to
2006 and so on, the code has to be changed to cur_year = 2006, cur_year=2005
and so on and so on. I want to manually set the year using code something
like this:
cur_year as integer
cur_year = year(date())
Thus with the year() function and the date() function, I hope to see the
year 2005 for the next few weeks and then the year 2006 and beyond as the
program continues to get used.
Something really confusing happned to me today as well wiht the code I am
seeing in this application. Within a user developed procedure, I have seen a
case statement such as the following:
Select Case EditYearVal
Case 95: jobtabname = 'ATS JOBS 1995'
linetabname = 'ATS LINES 1995'
Case 96 jobtabname = 'ATS JOBS 1996'
linetabname = 'ATS LINES 1995'
...
Case 2004 jobtabname = 'ATS JOBS 2004'
linetabname = 'ATS LINES 2004'
Case 2005 jobtabname = 'ATS JOBS 2005'
linetabname = 'ATS LINES 2005'
in my case, the case statment was as shown above with all the values from
1995 to 2005 (I just typed a few to show you what it looks like here). This
afternoon, I opened the code and did a database conversion from access 2.0 to
access 97 and then I split the database into a front end and a back end.
Both processes were successfully complted, but when I just checked the code
in the procedures or modules if you like, I saw a new case statement added to
this case statement and it was as follows:
Case 2006: jobtabname = 'ATS JOBS 2006'
linetabname = 'ATS LINES 2006'
note to this new case statement, I did not create any new tables for 2006
and no other case statements have been updated to this point. How in the
world could have this new case statement be added to the modules. If this
was possible, why was the code no modified to update itself else where.
What I need to know is how can I identify where the update takes place and
what I can do to stop it, as I would like to simply have all the use of the
case statement to be like the following:
Select case yearval
case 95: jobtabname = 'ATS JOBS 1995'
...
Case Else: jobtabname 'ATS JOBS AFTER 2005'
thus the case else would be used as a catch all to have all new values used
beyond the year 2005, inwhich this database is very year based.
I hope this makes sense and someone here can help me.
Edward Letendre.