DataSheet Sumary

[Cesarini]

Hi Guys/Girls,

Access 2007

I have a Datasheet form into another as a subform

I have a sumary texbox unbound in the first Datasheet, that takes the its
value from another unbound texbox placed into the subform. This works just
fine.The problem I need to solve is the sumary. This shows the value until I
click on the plus sign ("+") meanwhile it shows and error (#Error). I need
the sumary textbox recalculates its value always.As usual I will appreciate
your helpsRegards,

 

[Arvin Meyer [MVP]]

Add a footer to your subform. Ass a textbox to the footer. Do your
calculations there. They won't be seen on the main form BUT, you can refer
to them in a textbox that it seen. Use the control source:

=Forms!FormName!SubformName.Form!txtTextBoxName

 

[Cesarini]

Thanks for your Answer Arvin:

That's exactly what i have, but for some reason it does not work when I
fires the form en DataSheet view. I'm very interested to have it in that view
bacause it shows a tree groups. But i have the error message I post at the
begining

I really appreaciate you help about it.

Regards,

 

[Arvin Meyer [MVP]]

Try doing it again. Make sure that you are using the subform control's name,
not the name of the subform, (although they are often the same).
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access

 

[Douglas J. Steele]

Why would you? The former is the correct syntax.

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
(no e-mails, please!)

Arvin , can we change the code

from :
=Forms!FormName!SubformName.Form!txtTextBoxName

to
=Forms!FormName!SubformName!txtTextBoxName

Try doing it again. Make sure that you are using the subform control's
name,
not the name of the subform, (although they are often the same).

Thanks for your Answer Arvin:

[quoted text clipped - 36 lines]

.

 

[Douglas J. Steele]

What version of Access? Older versions let you be sloppy with the syntax:
Access 2007 (and presumably Access 2010) is much fussier, so using the
correct syntax is always a good idea.

Is there a particular reason why you don't want to use the correct syntax?

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
(no e-mails, please!)

i did simple test, both gave the same results..

Why would you? The former is the correct syntax.

Arvin , can we change the code

[quoted text clipped - 12 lines]

.

 

[Cesarini]

Hi Againg guys,

I´ve tried both ways, and they are giving me the "#Error" text instead of
the sumary amount.

As I said, the error message gets off and It shows the right amount after I
click in the "+" sign of the DataSheet.

Please I need to solve this. I have made tests too without sucess. :-(

I do not understand why the error comes up if I click directly in the forms
name in the Access toolbar. If I click in the view option in design mode, the
error disapear and the sumary is shown.

Many thanks for yours feedbacks

Regards

--
------------------
César Parrales

What version of Access? Older versions let you be sloppy with the syntax:
Access 2007 (and presumably Access 2010) is much fussier, so using the
correct syntax is always a good idea.

Is there a particular reason why you don't want to use the correct syntax?

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
(no e-mails, please!)

i did simple test, both gave the same results..

Why would you? The former is the correct syntax.

Arvin , can we change the code

[quoted text clipped - 12 lines]

.

.

 

[Douglas J. Steele]

My advice would be to correct it now before you add more lines of code.

As I've said, each version of Access has introduced stricter implementation
of syntax checking, so it's always possible that sloppy syntax may work now,
but not later.

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/djsteele
(no e-mails, please!)

Access 2007. I used that syntax in my applications. Have you heard
anywhere
that style will give problems in future?

i have application with >12000 line of codes. if that style will give me
trouble, better careful next time.
Your opinion much appreciated..

What version of Access? Older versions let you be sloppy with the syntax:
Access 2007 (and presumably Access 2010) is much fussier, so using the
correct syntax is always a good idea.

Is there a particular reason why you don't want to use the correct syntax?

i did simple test, both gave the same results..

[quoted text clipped - 5 lines]

.

 

[Cesarini]

Help would be helpful

Thanks,
--
------------------
César Parrales

My advice would be to correct it now before you add more lines of code.

As I've said, each version of Access has introduced stricter implementation
of syntax checking, so it's always possible that sloppy syntax may work now,
but not later.

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/djsteele
(no e-mails, please!)

Access 2007. I used that syntax in my applications. Have you heard
anywhere
that style will give problems in future?

i have application with >12000 line of codes. if that style will give me
trouble, better careful next time.
Your opinion much appreciated..

What version of Access? Older versions let you be sloppy with the syntax:
Access 2007 (and presumably Access 2010) is much fussier, so using the
correct syntax is always a good idea.

Is there a particular reason why you don't want to use the correct syntax?

i did simple test, both gave the same results..

[quoted text clipped - 5 lines]

.

.