Problem With CDec Function

[John Lane]

I have a query with one column containing "Expr1: CDec([ChkPmt])". When I try
to run or store the query, I get a message saying the function has the wrong
number of arguments. Is this yet another Microsoft bug? The function looks
good to me. Thanks.

 

[Jerry Whittle]

With the database open, press Ctrl + g to bring up the VBA window.

In the Immedieate window, paste in the following then hit Enter.

Debug.Print CDec("123.222")

Does it work there? If it does, it might be something else in the query
messing things up.

What version of Access? If 2007 did you enable options?

 

[J R]

yikes...

http://support.microsoft.com/kb/225931

I have a query with one column containing "Expr1: CDec([ChkPmt])". When I try
to run or store the query, I get a message saying the function has the wrong
number of arguments. Is this yet another Microsoft bug? The function looks
good to me. Thanks.

On Saturday, December 12, 2009 7:25 PM Jerry Whittle wrote:
With the database open, press Ctrl + g to bring up the VBA window.

In the Immedieate window, paste in the following then hit Enter.

Debug.Print CDec("123.222")

Does it work there? If it does, it might be something else in the query
messing things up.

What version of Access? If 2007 did you enable options?
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"John Lane" wrote:

 

[John W. Vinson]

Ummmm....

Why are you replying (pointlessly) to a two-year old message with a valid
answer?

yikes...

http://support.microsoft.com/kb/225931

I have a query with one column containing "Expr1: CDec([ChkPmt])". When I try
to run or store the query, I get a message saying the function has the wrong
number of arguments. Is this yet another Microsoft bug? The function looks
good to me. Thanks.

On Saturday, December 12, 2009 7:25 PM Jerry Whittle wrote:
With the database open, press Ctrl + g to bring up the VBA window.

In the Immedieate window, paste in the following then hit Enter.

Debug.Print CDec("123.222")

Does it work there? If it does, it might be something else in the query
messing things up.

What version of Access? If 2007 did you enable options?
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"John Lane" wrote:

--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com