cant set control source= anything in Access 2003

  • Thread starter Thread starter Michael San Filippo
  • Start date Start date
M

Michael San Filippo

i have a check register on a cont. form that I need to populate a running
sum on - i had the control source=runsum which was a function I had. I was
using fine w/ 2000 however now I notice with 2003 - if you set any control
source = to anything - whether it be a function or a dsum or anything it
gets stuck i a loop - any ideas?
 
From any code window, choose References on the Tools menu.
Anything marked "MISSING"? If so, see:
http://allenbrowne.com/ser-38.html

If that's not the case, do you have any conditional formatting on the
controls in this subform? If so, Access 2003 may get locked into a loop
where it does the conditional formatting and then does the calculated
controls, which triggers the conditional formatting again, which ...
 
Nope all references are correct

its very strange - i compiled the code - no errors - it has to do with a
controlsource equaling something besides a field in a table or query.

even something as simple as this -
=IIf([ysnVoid]=Yes,"VOID","")

As soon as I remove all fields that have this - it works flawlessly
 
Okay. What is the name of this control? If it is the same as a field name
(e.g. "ysnVoid") but bound to an expression, Access will get confused.
Rename.

Not sure Access will understand the word Yes in that context. Try -1, or
perhaps:
=IIf(Nz([ysnVoid], False), "Void", Null)

Also check the Format property of the box to ensure it is compatible with
text such as Void.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Michael San Filippo said:
Nope all references are correct

its very strange - i compiled the code - no errors - it has to do with a
controlsource equaling something besides a field in a table or query.

even something as simple as this -
=IIf([ysnVoid]=Yes,"VOID","")

As soon as I remove all fields that have this - it works flawlessly

Allen Browne said:
From any code window, choose References on the Tools menu.
Anything marked "MISSING"? If so, see:
http://allenbrowne.com/ser-38.html

If that's not the case, do you have any conditional formatting on the
controls in this subform? If so, Access 2003 may get locked into a loop
where it does the conditional formatting and then does the calculated
controls, which triggers the conditional formatting again, which ...
 
Name of that control is simply Text49

even happens on another text box called total with this as control source -
=DSum("dblbalance","checkreg")

this all worked when I was using Access 2002 and under, now that I have
upgraded the whole office to 2003 it wont work. HELP ;-)

Allen Browne said:
Okay. What is the name of this control? If it is the same as a field name
(e.g. "ysnVoid") but bound to an expression, Access will get confused.
Rename.

Not sure Access will understand the word Yes in that context. Try -1, or
perhaps:
=IIf(Nz([ysnVoid], False), "Void", Null)

Also check the Format property of the box to ensure it is compatible with
text such as Void.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Nope all references are correct

its very strange - i compiled the code - no errors - it has to do with a
controlsource equaling something besides a field in a table or query.

even something as simple as this -
=IIf([ysnVoid]=Yes,"VOID","")

As soon as I remove all fields that have this - it works flawlessly

Allen Browne said:
From any code window, choose References on the Tools menu.
Anything marked "MISSING"? If so, see:
http://allenbrowne.com/ser-38.html

If that's not the case, do you have any conditional formatting on the
controls in this subform? If so, Access 2003 may get locked into a loop
where it does the conditional formatting and then does the calculated
controls, which triggers the conditional formatting again, which ...

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

i have a check register on a cont. form that I need to populate a running
sum on - i had the control source=runsum which was a function I had.
I
was
using fine w/ 2000 however now I notice with 2003 - if you set any control
source = to anything - whether it be a function or a dsum or
anything
 
Once Access hits one calculated control that cannot be calculated, it gives
up on attempting any more. You may need to track down the one.

Alternatively, if no functions work, you may have a references problem:
http://allenbrowne.com/ser-38.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Michael San Filippo said:
Name of that control is simply Text49

even happens on another text box called total with this as control source -
=DSum("dblbalance","checkreg")

this all worked when I was using Access 2002 and under, now that I have
upgraded the whole office to 2003 it wont work. HELP ;-)

Allen Browne said:
Okay. What is the name of this control? If it is the same as a field name
(e.g. "ysnVoid") but bound to an expression, Access will get confused.
Rename.

Not sure Access will understand the word Yes in that context. Try -1, or
perhaps:
=IIf(Nz([ysnVoid], False), "Void", Null)

Also check the Format property of the box to ensure it is compatible with
text such as Void.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Nope all references are correct

its very strange - i compiled the code - no errors - it has to do with a
controlsource equaling something besides a field in a table or query.

even something as simple as this -
=IIf([ysnVoid]=Yes,"VOID","")

As soon as I remove all fields that have this - it works flawlessly

From any code window, choose References on the Tools menu.
Anything marked "MISSING"? If so, see:
http://allenbrowne.com/ser-38.html

If that's not the case, do you have any conditional formatting on the
controls in this subform? If so, Access 2003 may get locked into a loop
where it does the conditional formatting and then does the calculated
controls, which triggers the conditional formatting again, which ...

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

message
i have a check register on a cont. form that I need to populate a
running
sum on - i had the control source=runsum which was a function I
had.
I anything
 
Back
Top