From: Chegu Tom on
I recently had several machines running Access 2003 start showing errors
unexpecedly. When you installed the Office on your new machines it may
have updated to Service Pack 3, SP3

Machines running SP2 worked fine. Those that got the SP3 had problems. See
Allen Browne's article on the SP3 bugs
http://allenbrowne.com/bug-Access2003SP3.html

Check the version and SP level on machines that work and don't work. I had
to uninstall Office then reinstall and update to SP2 to make my problems go
away.

Tom


"klp via AccessMonster.com" <u19032(a)uwe> wrote in message
news:a53e1ccd2df50(a)uwe...
> Not sure if this is where I post this or can be answered here.
>
> Currently we have company software that is programmed by an outside
> programmer. We purchased the code to make any addtions or modifications.
> Each
> time there is a new release, I bring it in and make our custom
> modifications
> to it. Until now I have not had any problems. Note: we are using access
> 2003
> & windows 7 and before when I wasn't having any issues I was using XP. Now
> when I make modifications to a form for example I get errors in my memo
> fields. So I have a form frmItemMaster that has a tab control on it. I go
> in,
> add another tab and embed a form. If I open for the form put in a part
> number,
> go to my newly added tab then to another tab my memo field displays this
> #Error and if I click in it a msgbox comes up that says 'invalid
> argument'.
> That is if the field is blank and does not have any data in it. Otherwise
> if
> there is data in the field I can edit it. Not sure why these problems are
> arising and it has only started in windows 7. Like I said I'm not sure if
> I'm
> even posting in the right spot, and I'm sorry if I'm not, I just don't
> know
> what else to do. It just almost seems as if there is something, somewhere
> that's different in windows 7 causing this error.
>
> thanks in advance
> Kim P
>
> --
> Message posted via http://www.accessmonster.com
>