Prev: highlight current record in continious form
Next: Access 2010 misbehaving
From: Access Developer on 12 Aug 2010 00:47
"Salad" <salad(a)oilandvinegar.com> wrote

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

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


From: Salad on 12 Aug 2010 01:15
Access Developer wrote:

> "Salad" <salad(a)oilandvinegar.com> wrote
>
> > I call it .44 magnum corruption. Do you feel lucky?
>
> I thought Dirty Harry asked, "Feel lucky, punk?" <GRIN>
>
>
From the source. Enjoy. :)
http://www.youtube.com/watch?v=FnMLGkj91Og
From: sparks on 12 Aug 2010 09:15
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(a)SeeSignature.invalid> wrote:

>sparks <sparks(a)home.com> wrote in
>news:01t5669qntrk6gogbqsj9c423iq5r2fj80(a)4ax.com:
>
>> Repair did nothing to help this.
>
>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.
>
>> 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
>
>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.
From: David W. Fenton on 12 Aug 2010 19:49
sparks <sparks(a)home.com> wrote in
news:drs766tin8ftsiv9afaji9o3tnmbh5bj2e(a)4ax.com:

> 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.

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.

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

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/
First  |  Prev  | 
Pages: 1 2
Prev: highlight current record in continious form
Next: Access 2010 misbehaving