If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
starting access 97
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. |
#2
|
|||
|
|||
Edward Letendre wrote:
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. I find it a little hard to follow exactly what your situation is, so please excuse me if my answer is off target. Access can ask for several different kinds of passwords. One involves the workgroup. That may be what you now have. If the database you are opening is not secured, you likely do not need to long onto the workgroup. Look at the properties for the shortcut. Make a copy and clip off all the stuff after *.exe If that works, then it is not secured and you can use that shortcut. Don't delete the other one unless you are sure you don't need it for another database. You can startup the database while holding down the shift key and it should open without running the startup form (in this case the switchboard) If you have access you can change or eliminate the start up form in the tools area there is an option setting. -- Joseph Meehan 26 + 6 = 1 It's Irish Math |
#3
|
|||
|
|||
Joseph's answers are good ones; to expand a bit:
In a networked environment, it's best to split your database, and put the data on the server, with a separate copy of the front end on each desktop. In your case, this is especially desirable, because you can put an Access 97 version of the front end on the Access 97 machines, and an Access 2000 version on those machines. Be sure to leave the back end (data) in Access 97; Access 2000 can read Access 97 tables, but Access 97 cannot read Access 2000 tables. If you do any editing of the forms, etc in Access 2000, you'll need to save a copy back to Access 97 format for those users. Some issues may arise if you use features in Access 2000 which are not available in A97; you can avoid this by doing your development (editing) in A97. Do all of your users get the "not converted" message? Or only the Access 2000 users? HTH - Turtle "Edward Letendre" wrote in message ... 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. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Access 2003 (Ready to throw in the trash) | Patrick Parks | General Discussion | 5 | January 5th, 2005 10:38 PM |
WORD XP mail-merge FAILS using ACCESS query | SueMackay | Running & Setting Up Queries | 4 | November 29th, 2004 04:11 PM |
Adding staff photographs to my database | KK | New Users | 2 | September 3rd, 2004 07:41 AM |
Access user profile | Michael Breitsameter | General Discussion | 7 | July 23rd, 2004 07:47 AM |
You do not have exclusive access... ERROR | Robin | General Discussion | 1 | July 6th, 2004 01:18 AM |