[AccessD] Nz function in Access 2002

Well supposedly 2002 handles Nulls differently from earlier versions,
but I've seen no evidence of it.  However, if you used Len(<expression>)
in 2000 and earlier, and the expression was Null, you got an error, so
you had to use Len(<expression> & "") to avoid the error.  I haven't
tried it yet, but I can't say that I trust it.
 
Charlotte Foust

	-----Original Message-----
	From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com] On Behalf Of David McAfee
	Sent: Thursday, March 06, 2003 3:03 PM
	To: 'accessd at databaseadvisors.com'
	Subject: RE: [AccessD] Nz function in Access 2002
	
	
	Hmmm, in A97, I made a new form. Created the following sub:
	
	
	Private Sub Form_Load()
	MsgBox "Len(me.openargs) =" & Len(Me.OpenArgs)
	Stop
	End Sub
	 
	 
	The msgbox displays "Len(me.openargs) ="
	 
	so, I press Ctrl+G, and enter the following in the debug window
and get the following results:
	 
	?Len(me.openargs)
	Null
	?Len(me.openargs)>0
	Null
	?Len(me.openargs)=0
	Null
	?Len((me.openargs))
	 0 
	?isnull(me.openargs)
	True
	?isempty(me.openargs)
	False
	?nz(me.openargs)
	 
	?nz(me.openargs,0)
	 0 
	?nz(me.openargs)=""
	True
	?nz(me.openargs,"")=""
	True
	
	 
	It seems to me that the MS Len fix wouldn't work for OpenArgs
(or lack there of) validation
	Can someone try this in A XP (2002)?
	 
	David
	 

		-----Original Message-----
		From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of Charlotte Foust
		Sent: Thursday, March 06, 2003 1:01 PM
		To: accessd at databaseadvisors.com
		Subject: RE: [AccessD] Nz function in Access 2002
		
		
		But they don't need a fix, Charles.  After all, they
posted a "resolution" in the article! <vbg>  I'd just be happy if they
explained what it is that doesn't work!!
		 
		Charlotte Foust

			-----Original Message-----
			From: Wortz, Charles
[mailto:CWortz at tea.state.tx.us] 
			Sent: Thursday, March 06, 2003 12:40 PM
			To: accessd at databaseadvisors.com
			Subject: RE: [AccessD] Nz function in Access
2002
			
			
			I did a check of kbAlertz and there is no
follow-up KB article posted yet.  So whatever is the unstated problem
with NZ(), they haven't posted a fix yet.

			Charles Wortz 
			Software Development Division 
			Texas Education Agency 
			1701 N. Congress Ave 
			Austin, TX 78701-1494 
			512-463-9493 
			CWortz at tea.state.tx.us 

			-----Original Message-----
			From: William Hindman
[mailto:wdhindman at bellsouth.net] 
			Sent: Thursday 2003 Mar 06 14:27
			To: accessd at databaseadvisors.com
			Subject: Re: [AccessD] Nz function in Access
2002
			
			
			...this is a prime example of Microsoft geek
writing ...the reason I never buy anything from MS Press ...I'll be
damned if I can figure out what it is that the nz function doesn't quite
perform "as expected"? :(
			 
			...I use nz in several AXP apps and to date have
noticed nothing that I didn't expect ...but with this kind of crap KB,
I'll be certain to waste a lot of time the next time I use it, just
futzing about looking for some kind of error in the returned data :(((((
			 
			...I don't know whether to thank Charlotte for
pointing this out or mail her my dirty laundry instead :(
			 
			William Hindman ...ok, I won't mail her my dirty
laundry ...probably upset my post lady :)

				----- Original Message ----- 
				From: Charlotte Foust
<mailto:cfoust at infostatsystems.com>  
				To: AccessD at databaseadvisors.com 
				Sent: Thursday, March 06, 2003 1:56 PM
				Subject: [AccessD] Nz function in Access
2002


				I ran across an MSKB article today
http://support.microsoft.com/default.aspx?scid=kb;en-us;295619
<http://support.microsoft.com/default.aspx?scid=kb;en-us;295619>  that
says the Nz function works in 2002 but it may not work as expected!  Say
what??   It works, but it doesn't?

				Has anyone run into this?  Nz isn't
always the most appropriate function, but I've never seen it fail, at
least not that I knew about.  We use this a lot, and I'm concerned about
migrating our apps from 97 to 2002 and having a lot of code fall over.
I wondered if it could be the result of not passing in the optional
argument, but the article seemed rather vague to me.  Does anyone else
have first-hand knowledge of the problem?

				Charlotte Foust 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030306/52751cbd/attachment-0001.html>