Many thanks once again Allen.
I didn't check the auto correct thing when I upgraded from A97.
Have done now though, so I hope that will be the solution. Being an
intermittent problem, I'll need to wait and see.
Thanks again.
--
Bob Darlington
Brisbane
"Allen Browne" <AllenBrowne@SeeSig.Invalid> wrote in message
news:420cbfff$0$25052$5a62ac22@per-qv1-newsreader-01.iinet.net.au...[color=blue]
> Hi Bob
>
> It probably is a corruption, and there are at least 3 things that can
> cause this.
>
> 1. The first is Name AutoCorrect. Make sure you uncheck those boxes under:
> Tools | Options | General
> Then compact the database again.
> Explanation of why:
>
http://members.iinet.net.au/~allenbrowne/bug-03.html
>
> 2. If the form has a subform, the next thing to try is to open the subform
> in design view, and add a text box for the foreign key field, i.e. the one
> names in the LinkChildFields property. There seems to be a bug in A2002
> and A2003 where it crashes if this property refers to an AcessField, and
> you can work around the bug by placing a text box on the form so it refers
> to a Textbox type object instead.
>
> 3. The other likely cause is a corruption where the compiled code is out
> of sync with the text version. Decompile a copy of the database by
> entering something like this at the command prompt while Access is not
> running. It is all one line, and include the quotes:
> "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
> "c:\MyPath\MyDatabase.mdb"
> Then compact again.
>
> If that still doesn't work, create the new mdb and make sure Name
> AutoCorrect is off in the new one before you import everything.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users -
http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Bob Darlington" <bob@dpcmanAX.com.au> wrote in message
> news:420c34d8$0$5725$afc38c87@news.optusnet.com.au ...[color=green]
>> Thanks Pieter,
>> Yes, I ran c/r and decomp, but to no avail.
>> It doesn't seem to be particular about which form is open. But I guess it
>> could still be some other object which is corrupt.
>> I'll try importing all into a new db (when I can).
>>
>> --
>> Bob Darlington
>> Brisbane
>> <pietlinden@hotmail.com> wrote in message
>> news:1108095693.375669.195220@l41g2000cwc.googlegr oups.com...[color=darkred]
>>> did you run a compact/repair? Sounds like corruption in your form to
>>> me. That said, I have never had what you describe happen to me. But
>>> corrupt objects will cause this kind of totally bizarre behavior.[/color][/color]
>
>[/color]
