[AccessD] ReadDirectoryChangesW, not returning anything to t he buffer.

Odd.  Although I have a preference for longs myself, it turns out that a 
number of standard Access functions use other numeric types so there is 
little need to look for old API calls to run into these.  For example, the 
mouse cooridinate parameters in a mouse move, down or up event are singles 
even though the values are always 'whole' numbers while the button and shift 
parameters are integer types.  The standard cancel parameter for open events 
is also typed as an integer and you had better dimension a compatible 
numeric type if you are passing a value to one of these standard procedures 
as a variable, though the mouse parameters are technically return or read 
only values 'returned' by a sub procedure.  My rule is to use a compatible 
type and if a long will work, that's the ticket.

Hen



>From: Drew Wutka <DWUTKA at marlow.com>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "'Access Developers discussion and problem solving'" 
><accessd at databaseadvisors.com>
>Subject: RE: [AccessD]  ReadDirectoryChangesW, not returning anything to t 
>he buffer.
>Date: Wed, 10 Sep 2003 18:05:01 -0500
>
>LOL.  Very funny.
>
>I do use int for all integers, because I always dimension as Long, unless I
>absolutely require an integer (which is only for API calls)
>
>Drew

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail