E
Edward Letendre
Okay, I have a question for the expers in access 97. I have an application
that runs on a older computer. The short cut was created on the desktop and
when a user clicks on the shortcut, the database starts up, and asks for a
password. Then the main switchboard is loaded for the database and the
database is up and running.
My question is as follows. I am used to just starting Access 97 in edit
mode with the ability to access the tables, forms, etc. How do I get the
database to open in edit mode rather than with the swtich board up and
running.
Also this database was orginally developed in access 2.0 and was converted
to access 97 (I am not sure how as I was not around when the orginal database
was developed). But everytime the database is opened, the users get the
error message saying that the database cannot be converted or that it was not
converted correctly. I have tried to open the database in exclusive mode,
but with the way it was opened/converted the first time, it cannot be opened
in exclusive mode.
As a last resort, I was looking at moving the entire application from access
2.0/access 97 into access 2003 and creating a runtime application that can be
shared across the network on all desktops (4 to 5 workstations accessing the
same application and tables, etc.). I would need some info on how to open or
get the data out of access 97 and into access 2003 (table, forms, etc).
The users of the application want to be able to have the database shared out
across the network, as the datbase is located in a network drive but is
available on one machine only.
If I left it in access 97, how hard would it be to get it converted
correctly and have multiple users access the application without any errors
occuring (including any corrupted tables or rows, etc.)?
Finally, the last problem is that there are uses here with many version of
access (access 97 and access 2000, but no versions of access 2003 as of yet).
If I was to go with access 2003 and create a shared runtime executable of
the database, how hard would this be? I have some experience with Oracle
(working on my OCP for 8i) and thus I have some experience with databases.
It is just that I cannot get access to open this database without opening the
switch board and I have the converstion error as it seems that the database
was not correctly converted from access 2.0 to access 97 in the first place.
I guess to complicate matters worse is that there has been alot of data
added to the database as it has been running in access 97 as a badly
converted application.
Help me if you can.
Edward Letendre.
that runs on a older computer. The short cut was created on the desktop and
when a user clicks on the shortcut, the database starts up, and asks for a
password. Then the main switchboard is loaded for the database and the
database is up and running.
My question is as follows. I am used to just starting Access 97 in edit
mode with the ability to access the tables, forms, etc. How do I get the
database to open in edit mode rather than with the swtich board up and
running.
Also this database was orginally developed in access 2.0 and was converted
to access 97 (I am not sure how as I was not around when the orginal database
was developed). But everytime the database is opened, the users get the
error message saying that the database cannot be converted or that it was not
converted correctly. I have tried to open the database in exclusive mode,
but with the way it was opened/converted the first time, it cannot be opened
in exclusive mode.
As a last resort, I was looking at moving the entire application from access
2.0/access 97 into access 2003 and creating a runtime application that can be
shared across the network on all desktops (4 to 5 workstations accessing the
same application and tables, etc.). I would need some info on how to open or
get the data out of access 97 and into access 2003 (table, forms, etc).
The users of the application want to be able to have the database shared out
across the network, as the datbase is located in a network drive but is
available on one machine only.
If I left it in access 97, how hard would it be to get it converted
correctly and have multiple users access the application without any errors
occuring (including any corrupted tables or rows, etc.)?
Finally, the last problem is that there are uses here with many version of
access (access 97 and access 2000, but no versions of access 2003 as of yet).
If I was to go with access 2003 and create a shared runtime executable of
the database, how hard would this be? I have some experience with Oracle
(working on my OCP for 8i) and thus I have some experience with databases.
It is just that I cannot get access to open this database without opening the
switch board and I have the converstion error as it seems that the database
was not correctly converted from access 2.0 to access 97 in the first place.
I guess to complicate matters worse is that there has been alot of data
added to the database as it has been running in access 97 as a badly
converted application.
Help me if you can.
Edward Letendre.