I have 1 subform in an access 2003 database that any time I put a
option group on it and hit save the database crashes.
Any other type of control is not a problem. Check box, toggle button
.....etc
I have even put about 10 different types of controls on the form tied
to variables and still it works fine.But not an option group

The subform is tied to a table with 12 variables and there are 16
controls on the subform.

I can put the same option group on any other form and save with no
problems.

On Wed, 11 Aug 2010 08:12:31 -0500, sparks <sparks (AT) home (DOT) com> wrote:

You seem to have some form of corruption. Repair&Compact the database.
If that does not help, export this form to text using the undocumented
Application.SaveAsText method. Then import all objects except this one
to a new database using the normal "External Data" method, and import
this one using LoadFromText.

-Tom.

Repair did nothing to help this.
Very strange since I can drop that control on any form in the database
and its fine except this one.
I made a new form and put all the controls on it. Saved and exit
went in and added the option group and it worked fine.
What type of corruption is this called, when you can add anything to a
form but one type of control?
micro what LOL

I have tried the saveastext before but how do you load only the one
control we are talking about ?


On Wed, 11 Aug 2010 07:01:40 -0700, tom7744.no.spam (AT) cox (DOT) net wrote:

sparks wrote:

I call it .44 magnum corruption. Do you feel lucky?

sparks <sparks (AT) home (DOT) com> wrote in
news:01t5669qntrk6gogbqsj9c423iq5r2fj80 (AT) 4ax (DOT) com:

That's not surprising. It would be a very, very unusual situation
that corruption of the Jet/ACE data structures would cause a crash
on actions taken in form design. Only corruption of the VBA project
could lead to that, and a compact is not going to have any effect on
that whatsoever.

Did you simply ignore the rest of the instructions you were given to
try SaveAsText? Or did you just choose not to mention it in your
answer?

I wouldn't bother with that until I'd done a decompile, though.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

"Salad" <salad (AT) oilandvinegar (DOT) com> wrote

I thought Dirty Harry asked, "Feel lucky, punk?" <GRIN>

Access Developer wrote:

http://www.youtube.com/watch?v=FnMLGkj91Og

Well the dump would not include the offending control I am trying to
put on the form. As soon as it is placed on the form the program
crashes.

So basically you would just save and import just like copying all the
controls to a new form like I did.



On 11 Aug 2010 20:57:48 GMT, "David W. Fenton"
<NoEmail (AT) SeeSignature (DOT) invalid> wrote:

sparks <sparks (AT) home (DOT) com> wrote in
news:drs766tin8ftsiv9afaji9o3tnmbh5bj2e (AT) 4ax (DOT) com:

The assumption behind the recommendation is that the form is
corrupted, and that saving it out and recreating it would remove the
corruption so that dropping the control on the form would no longer
crash Access.

Eh?

If you do a SaveAsText on the form before the control has been
dropped on the form, you would then to a LoadFromText to get an
exact duplicate of that form that should not have any corruption in
it. Then you should be able to drop the option group on it, delete
the old corrupted one and work from the new one.

One thing to check:

Do you have the form wizards turned on? It could be that the wizard
is what's causing the crash. Turn it off and try dropping the option
group on the form.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

Great tip! This worked a treat for almost the identical problem the original poster had - ie option group causing form to crash out with memory error. Thanks heaps.