By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,931 Members | 1,247 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,931 IT Pros & Developers. It's quick & easy.

#Error in Form Footer Total

P: n/a
jv
Hello,
I have a continuous form that has a textbox named InvoiceAmount. This
textbox is not a calculated field. It's control souce is a field also
named InvoiceAmount in the tblInvoices table. In the form footer, I
have a textbox name txtBatchTotal which should show the sum of all
invoices in the batch. The control source of txtBatchTotal is
=Sum([InvoiceAmount])

This gives me a #Error in the txtBatchTotal field.

I should mention that I'm using Access 2002 ADP with SQL 2000. Please
let me know if you have any suggestions.

Thanks.

Julie Vazquez

Nov 13 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
On 29 Dec 2004 16:01:11 -0800, "jv" <ju***********@hotmail.com> wrote:

Check the NorthwindCS sample application, the Orders form. Its subform
has a similar setup as what you're describing. Compare carefully and
you should find the root cause.
My guess: a typo in the expression.

-Tom.

Hello,
I have a continuous form that has a textbox named InvoiceAmount. This
textbox is not a calculated field. It's control souce is a field also
named InvoiceAmount in the tblInvoices table. In the form footer, I
have a textbox name txtBatchTotal which should show the sum of all
invoices in the batch. The control source of txtBatchTotal is
=Sum([InvoiceAmount])

This gives me a #Error in the txtBatchTotal field.

I should mention that I'm using Access 2002 ADP with SQL 2000. Please
let me know if you have any suggestions.

Thanks.

Julie Vazquez


Nov 13 '05 #2

P: n/a
jv
I've checked the spelling very carefully about 10 times and have
deleted the control and recreated from scratch. The expression works
with =[InvoiceAmount], but return #Error when I put Sum() or Max()
around it like in =Sum([InvoiceAmount]). It is very strange.

Nov 13 '05 #3

P: n/a
jv
I also found that when my form's record source is simply tblInvoices,
=Sum([InvoiceAmount]) in the form footer works fine. However, when the
form's records source is a joined query, that's when I get #error for
=Sum([InvoiceAmount]) and =Sum([tblInvoices].[InvoiceAmount]).
Does anyone know why this may be?

thanks.

Nov 13 '05 #4

P: n/a
jv wrote:
I've checked the spelling very carefully about 10 times and have
deleted the control and recreated from scratch. The expression works
with =[InvoiceAmount], but return #Error when I put Sum() or Max()
around it like in =Sum([InvoiceAmount]). It is very strange.


Are you sure you put this control in the form footer and not the page footer?

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #5

P: n/a
jv
I finally tried saving my form's record source Select statement as a
view and used that view as the record source. Somehow that solved my
problem. I have no idea why.....

Nov 13 '05 #6

P: n/a
On 30 Dec 2004 08:38:13 -0800, "jv" <ju***********@hotmail.com> wrote:

I've noticed this too: Access ADP really likes views.
-Tom.
I finally tried saving my form's record source Select statement as a
view and used that view as the record source. Somehow that solved my
problem. I have no idea why.....


Nov 13 '05 #7

P: n/a
Tom van Stiphout wrote:
On 30 Dec 2004 08:38:13 -0800, "jv" <ju***********@hotmail.com> wrote:

I've noticed this too: Access ADP really likes views.
-Tom.


Yes it does ...
except on anniversaries of major battles of either the Punic Wars or the
Wars of the Roses
or when the distance (km) of the earth's equator from the center of the
planet Mars is a multiple of 10000
or when you have a deadline to meet and it's ... tomorrow!

On such occasions you can pretty well bet that your ADP will NOT like
Views, it will like a SPROC, or a table returning UDF, or a T-SQL script
string, and that you may require several hours to discover just which of
these, if any, it does like, and how to implement its use in precisely
the manner that the Access ADP wants.

Arggggggggggghhhhhhhhhhh! The time that Access saved me from 1992(?) to
2002 has been entirely lost in the past two years coping with Access ADP
Arcane Anomalies ... never AGAIN!

(...first rant of 2005!)

Nov 13 '05 #8

P: n/a
jv
I thought that changing the form's record source to a view solved my
problem, but it didn't. The form total is OK until I need to refresh
or requery the form. At which point, the #error returns.

Does anyone know what's going on and how I can get rid of this problem?
Thanks.

Nov 13 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.