allochthonous
Technical User
Hello.
I am a mostly self taught Access newbie with only 6 months experience. I have had a couple of light online courses and a LOT of help from a coworker/friend with quite a bit of Access knowledge. I have been developing a front end/back end database in Access 2000 for work, to be used on a network. The back end will be located on the network, with the front end users having their own local copy of the front end. The back end contains all data entry tables, data compilation queries, and reports. Currently the project has 26 tables (5 linked to external sources), 390 queries, 25 forms, 15 macros, and 481 reports. I would say that I am 80-90% finished and have begun some light beta testing. Though it seems like an impressive piece of work to me, I realize that it is probably not much when compared to other "professionally" built databases.
Here is my problem:
I had just finished creating a bunch of reports and assigning the reports to the corresponding buttons on my latest report menu form. After I closed the database and reopened it, I received a warning: "The Visual Basic for Applications project in the database is corrupt." From then on, I could not do anything without that error message popping up and could no longer even access the VBA code. Luckily, I keep an archive of every day's work at the end of the day, so I had only lost about 2-3 hours of work. I reverted back to the previous version, but ran into the same problem after creating a few reports. My coworker is currently using Access 2003, so we tried to run my database through it, and it seemed to work OK, but I was skeptical. Also, not all of the users of my database may have access to 2003, so I wanted to keep it as 2000 friendly as possible.
I had been working off of a JumpDrive, so my next thought was to eliminate that as a variable. So I copied the last stable version onto my desktop and tried again, but had the same results. Next, I tried another desktop to eliminate that, with the same results once again. Frustrated, I then decided to see of I could determine at which point exactly the "corruption" began. I added the reports and code behind the buttons, saving, closing, and reopening after each one. After the fifth report was created and button activated, the database crashed on opening. I retraced my steps once again, and once again, it failed at the exact same point. My next thought was that perhaps this button was related to the cause, so decided to skip that row of buttons altogether. After retracing my steps again, it failed at the same point, except in the next row.
Running out of ideas, I even tried importing the form from a previous build and renaming it, but that did not work either.
My only option at this point was to try Access 2003. I hopped over to a machine that had 2003 running and opened the last stable build. It took a bit to open, but then worked just fine. I was able to move quite a ways past the point where it usually broke down. Curious, I decided to take it back over to 2000 to see what would happen now that I had built quite a bit past the threshold. Of course, I received the error.
OK, does ANYONE have any idea what is going on here? I cannot fathom that I have pushed the limitations of Access 2000. What threshold am I crossing here? Should I just move forward with 2003?
Please advise!!
Paul
I am a mostly self taught Access newbie with only 6 months experience. I have had a couple of light online courses and a LOT of help from a coworker/friend with quite a bit of Access knowledge. I have been developing a front end/back end database in Access 2000 for work, to be used on a network. The back end will be located on the network, with the front end users having their own local copy of the front end. The back end contains all data entry tables, data compilation queries, and reports. Currently the project has 26 tables (5 linked to external sources), 390 queries, 25 forms, 15 macros, and 481 reports. I would say that I am 80-90% finished and have begun some light beta testing. Though it seems like an impressive piece of work to me, I realize that it is probably not much when compared to other "professionally" built databases.
Here is my problem:
I had just finished creating a bunch of reports and assigning the reports to the corresponding buttons on my latest report menu form. After I closed the database and reopened it, I received a warning: "The Visual Basic for Applications project in the database is corrupt." From then on, I could not do anything without that error message popping up and could no longer even access the VBA code. Luckily, I keep an archive of every day's work at the end of the day, so I had only lost about 2-3 hours of work. I reverted back to the previous version, but ran into the same problem after creating a few reports. My coworker is currently using Access 2003, so we tried to run my database through it, and it seemed to work OK, but I was skeptical. Also, not all of the users of my database may have access to 2003, so I wanted to keep it as 2000 friendly as possible.
I had been working off of a JumpDrive, so my next thought was to eliminate that as a variable. So I copied the last stable version onto my desktop and tried again, but had the same results. Next, I tried another desktop to eliminate that, with the same results once again. Frustrated, I then decided to see of I could determine at which point exactly the "corruption" began. I added the reports and code behind the buttons, saving, closing, and reopening after each one. After the fifth report was created and button activated, the database crashed on opening. I retraced my steps once again, and once again, it failed at the exact same point. My next thought was that perhaps this button was related to the cause, so decided to skip that row of buttons altogether. After retracing my steps again, it failed at the same point, except in the next row.
Running out of ideas, I even tried importing the form from a previous build and renaming it, but that did not work either.
My only option at this point was to try Access 2003. I hopped over to a machine that had 2003 running and opened the last stable build. It took a bit to open, but then worked just fine. I was able to move quite a ways past the point where it usually broke down. Curious, I decided to take it back over to 2000 to see what would happen now that I had built quite a bit past the threshold. Of course, I received the error.
OK, does ANYONE have any idea what is going on here? I cannot fathom that I have pushed the limitations of Access 2000. What threshold am I crossing here? Should I just move forward with 2003?
Please advise!!
Paul
