vb123.com

Garry Robinson's Popular MS Access, Office and VB Resource Site

 

Home  Contact Us
Order our Software

RSS & Newsletter  
Join our XML/RSS Newsfeed or sign up for our informative newsletter on Office Automation, Access and VB topics
Read More

Get Good Help
If you need help with a database, our Professionals could be the answer
Read More

  Is Your Database Corrupt ?
If you have a corrupt database, Try our Access Recovery service

The Workbench  Find out who has your database open, start the correct version of Access, easy compacting and backups, change startup options, mde compile,  shutdown database Read and Download

The Toolshed 
Searchable help file comprising of all the information at vb123.com plus hidden downloads etc. Read More



The Toolbox

Libraries of software that we regularly import into our projects. Enhances the Toolshed More..


DryToast New
Backup and query your BaseCamp
® projects
Read More


Datamining/Graphs

Explore your data with this versatile graphing and data mining shareware tool. 
Read More

Garry's Blog
Find out a few other things that Garry has been writing about Microsoft Access. Read more

About The Editor Garry Robinson writes for a number of popular computer magazines, is now a book author and has worked on 100+ Access databases. He is based in Sydney, Australia
Contact Us ...

Search ...

or try our Aussie
 vb123.com.au
  mirror site

 

Next Tip  Access 2000 97 and 95 - illegal operation everytime a certain form is opened

If you get this message when you start up an Access 95/97 application or clicking on button in a form

Don't panic, there is an easy solution. First rename the form that is causing the problems to something like Formxxx. Then open that renamed form in design mode and Save As back to the original form name. When the new form has been checked, delete the old form.

There is a more potent version of this error that occurs when the form that is started by the Autoexec macro in the database becomes Illegal. This means that you cannot get into the database. What you need to do is hold down the shift key when you open the database in Explorer. This will start up the database without using Autoexec.

In Access 97, you can get this same message when doing a full compile of the database.  First try this trick on the objects that you have recently worked on.   If that doesn't work, maybe you should try a new database and import all objects into the database.  If you are into libraries, after you do this, reset the Project Name under advanced options to its correct name.  Keep a zipped copy of the old database around for a little while in case you didn't import all the objects.

If these fails, import all your objects into a brand new database but keep the most recent till last and import them one at a time.  Keep compiling each form until you hit the culprit.  One form that I had recently wouldn't fix under any circumstances.  I ended up making a new form and copying the controls into it.  Then I copied the vb from the old form into a text editor and then copied the text into the new form.  Then I deleted the old form.  2 hours of my life wasted on this little baby.

Garry Robinson   www.gr-fx.com  Sydney Software Consultant.

Garry -

referring to your toolshed:

toolshed\99\formbugs.htm

i had the same problem in Access2000. where even if i switch to the VBE and try to change just one thing, the second I click on save, the file is shut down.

I then tried to import all the forms, modules classes and did did the rename save as trick you mentioned. It's a hassle but saved me a 9 months worth of work.

Thought this would be nice to mention to you

Thanks a lot

TahaK - Owner of The Toolshed.

 

 

Links >>>  Home | Search | Workbench | Orders | Newsletter | Access Security | Access professionals