Re: Compile errors when using form control's "Control Source" property to refer to the control's value
From: Allen Browne (AllenBrowne_at_SeeSig.Invalid)
Date: 11/05/04
- Next message: cvegas: "Application-defined or object-defined error message"
- Previous message: Dirk Goldgar: "Re: dao syntax error, Help!"
- In reply to: Yarik Mezheritskiy: "Re: Compile errors when using form control's "Control Source" property to refer to the control's value"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Nov 2004 09:56:59 +0800
Hi Yaroslav
Have you ever had an intermittent bug, i.e. one that's triggered by some
combination of circumstance, but not another? I don't have the resources or
inclination to try to track this bug down for Microsoft, but it is triggered
only by the interaction of certain conditions, and I don't know what they
are. It could be triggered by anything, even as unobvious as adding the
128th control to a form.
Your Office SP is good. Check that you have SP8 for JET 4 as well. Locate
msjet40.dll (typically in windows\system32), right-click and check on the
Version tab. SP8 is indicated the minor version starting with 8, i.e.:
4.0.8xxx.0
This is at least as important as the Office SP. In fact, we display this on
the Help | About screen for our clients, using the API calls from:
http://www.mvps.org/access/api/api0065.htm
http://www.mvps.org/access/api/api0010.htm
-- 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. "Yarik Mezheritskiy" <yarik@garlic.com> wrote in message news:469b4bf5.0411041224.2b212c97@posting.google.com... > Thank you Allen! Your response is very helpful, indeed. (Especially > information about potential problems with using AccessField objects.) > > There is at least one thing though that still is not clear to me: Why > could two installations of MS Access 2000 SP3 react differently on the > very same code in the very same project? > > The code is in a subform and (as I know now) tries to reference an > AccessField object in the top-level form, like this: > > Me.PartID > > Why one installation of MS Access 2000 SP3 accepts this expression > (and interpretes it as intended) at run-time, while the other > installation issues compile error? Maybe I need to install some > patch(es), service pack(s), whatsoever on the poor second computer? > > FWIW: This is what I believe is currently installed on the "failing" > computer: > > - MS Access 2000 as a part of MS Office 2000 Professional SR-1 > - MS Office 2000 Service Pack 3 > - MS Office 2000 Developer SR-1 > > Maybe there is something else I need to install? Maybe I should have > been installing these things in some particular order or do some other > weird things (like, for example, installing MS Office 2000 Service > Pack 2 before installing MS Office 2000 Service Pack 3)? > > Or is it simply a nature of quirks of MS Access compiler and > interpreter: to _rnadomly_ complain or not complain about certain > things? > > Thank you, > Yaroslav.
- Next message: cvegas: "Application-defined or object-defined error message"
- Previous message: Dirk Goldgar: "Re: dao syntax error, Help!"
- In reply to: Yarik Mezheritskiy: "Re: Compile errors when using form control's "Control Source" property to refer to the control's value"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
