Adding Unbound Control Causes Critical Error

[joebb3]

I have a couple forms in my front end that cause Access to crash if I try adding any unbound controls to them.

Once the form crashes, it becomes inaccessable via the DB Window (Design AND Open). The code for the form stays in tact (thankfully).

The form that annoys me most is just a Main Menu. It has a few buttons on it a few Labels and that's it! There is a bunch of code OnLoad, but nothing out of the ordinary. It all works fine. But I try to add a textbox that shows the current Version of the app and it crashes.

Nothing fancy:

Me!Textbox = "Version: " & CurrentVer

Once I save... Blammo!

I'm starting to wonder if my Access Install is corrupt.

 

[joebb3]

Ok... I realized part of it... I should be using a Label placeholder and changing the caption...

But adding the control shouldn't cause a fatal error should it?

 

[GKChesterton]

I don't have any insights. I suggest you say what version Access you're on.

I don't think using a text box should be any worse than a label. I wondered if CurrentVer is a dedicated keyword, but no.

I think technically you described a bound control, just not bound to a recordset (I may be wrong on that); can you insert an unbound control with blank control source? Can you isolate any other specifics?

I've had more than one glitch that can't be explained. Sometimes the solution is to reinstall MS Access, but more often it's a corruption of the file; so I must work from a back-up and rebuild. Of course decompile before all that.

[purple]If we knew what it was we were doing, it would not be called
research [blue]database development[/blue], would it? [tab]-- Albert Einstein[/purple]​

 

[TheAceMan1]

How are ya joebb3 . . .

[blue]CurrentVer[/blue] causes me to raise an eyebrow. Try:

[blue]   Me!Textbox = "Version: " & [purple][B][I]Application.Version[/I][/B][/purple][/blue]

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[joebb3]

Thanx ya'll for replying...

TheAceMan1, Good! I ope you are the same!

Sorry! The code was just an example. "CurrentVer" is just a variable that I use to hold the current version of MY database. Not Access itself. That way I can put the Frontend Version on the main menu... Asthetics, ya know...

Its driving me nuts! I have a continuous form (a sub form of a parent form) that I tried to add a BOUND control to and... BLAMMO!

I'm leaning toward a bad install.

Can anyone think of any other reason?

 

[joebb3]

Opps... Can't find the edit post button.

Using Access 2K3.

 

[TheAceMan1]

joebb3 . . .

Just what access version are you using? ... I sure hope its not 2007

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[TheAceMan1]

joebb3 . . .

Sure sounds like corruption!

Have you tried copying all frontend objects to a new DB? ... be sure to backup your origional 1st.



See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[joebb3]

Ace,

Yup... I inherited this 7 yo database and completely cleaned it up and fixed YEARS old errors. After the clean up, I transfered everthing into a brand new Access 2K3 database.

Funny thing is, when this happens, the FORM becomes inaccessable, but the VBA is still all there.

I just had it happen again on an entirely new database I'm creating. I added an unbound text box to an unbound form and BLAMMO!!! 3 hours work gone. (I know.. I should have backed up.) Concidering my code is in tact, I think I can recreate the form I was working on pretty quickly.

I think its in the calculation! I was trying to display the sum of a column. Like: =Sum(me!listbox.column(3))

Still looking for alternatives! I'd hate to have to have Access re-pushed to my machine! (Large Corperate Intranet... Everthing is installed by Radia)

Joe

 

[GKChesterton]

List boxes are really cool. But they aren't little Excel spreadsheets.

[purple]If we knew what it was we were doing, it would not be called
research [blue]database development[/blue], would it? [tab]-- Albert Einstein[/purple]​

 

[TheAceMan1]

joebb3 . . .

We already have enough indications of corruption in the thread to warrent parsing thru the following link:

Access Database Corruption Repair Guide

[blue]Your Thoughts? . . .[/blue]

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]