Unwanted code formatting help.

[raskew]

Hi -

Situation: (A97) When attempting to write code in either a standard or form module on a particular computer (and I believe this to be computer-related), the cursor continually tries to eliminate blank spaces, backing up and eliminating necessary spaces. Example:

Dim db as DAO.Database
--unless you move real fast, becomes--
DimdbasDAO.D

Intellisense is effectively disenabled. The combo-box appears, following entering the period (.) but just flashes and then it's gone. I've seen this before but don't even know what to search on. Has anyone seen this? Is it an AutoCorrect problem and, if so, how to make it go away?

Once had a similar problem where, if encoding "Dim db as Database", it would return 'DIM DB AS DATABASE". You had no say in the matter--it was going to return All Caps whether you wanted it or not. The working solution was bizarre and involved creating an object e.g. form and naming it DATABASE, then closing the working database, reopening it and deleting the object. Amazingly, the problem disappeared and from then on, Dim db as Database worked as advertised. Who would've thought? Am wondering if this is one of those truly strange solutions.

Any wisdom greatly appreciated.

Thanks - Bob

 

[pbaldy]

I've seen the "disappearing intellisense" problem when there was an open form with a timer event running. That's what I'd check first.

 

[raskew]

Paul -

Good point! Will check this out when I have the opportunity to get back on the errant database.

Thanks for that, think you may be on the right track! Appreciate your input!

Bob

 

[raskew]

Paul -

You hit the nail on the head. Had a clock/calendar running on the main form. Closed the main form and the entire problem disappeared.

Really appeciate the advice. Thanks!

Bob

Added: Originally stated that I thought it was a computer-related problem, and still think it may be. The db in question is stored on a zip-drive. On computer A (home CPU), the problem rears its ugly head. On computer B (work standalone), not a problem! Up until a few days ago, the home CPU didn't have a problem either. The db in question has run for 3+ years. There's been no change to the clock/calendar (timer driven) control.

Any further thoughts appreciated.

 

[Pat Hartman]

Changing code while the timer was running may have corrupted the database. Try the /decompile and copying all objects into an empty db solutions to see if that fixes the problem.

 

[raskew]

Hi Pat -

Have looked at dozens of posts that somehow reference "Decompile", but don't really talk about how to impose the technique.

Knowing that this subject is totally unexplained in the Help Files, would you, if you're comfortable with it, expound on how to invoke the "Decompile" option. Example: I've got D:\db12.mdb. After backing it up, want to decompile then recompile.

Please help a dummy out and explain step by step how one would perform the process.

Appreciate it. -- Bob

 

[Pat Hartman]

you need to start your application from the Run command on the Start menu. Type in the name of your database followed by the switch.

yourdatabase.mdb /decompile

If you have multiple versions of Access installed you will need to include Access:

C:\xxxx\MSAccess.exe yourdatabase.mdb /decompile

And, if you use special characters or spaces in your directory names, you'll need to put quotes in appropriate places.