[AccessD] SysCmd constant conflict

Hi Susan,

This type of stuff is fairly common in the windows API.  

Take GetOpenFileName for instance.  Here is a list of the constants that I
have in one of my modules.

Const OFN_ALLOWMULTISELECT = &H200
Const OFN_CREATEPROMPT = &H2000
Const OFN_EXPLORER = &H80000
Const OFN_FILEMUSTEXIST = &H1000
Const OFN_HIDEREADONLY = &H4
Const OFN_NOCHANGEDIR = &H8
Const OFN_NODEREFERENCELINKS = &H100000
Const OFN_NONETWORKBUTTON = &H20000
Const OFN_NOREADONLYRETURN = &H8000
Const OFN_NOVALIDATE = &H100
Const OFN_OVERWRITEPROMPT = &H2
Const OFN_PATHMUSTEXIST = &H800
Const OFN_READONLY = &H1
Const OFN_SHOWHELP = &H10

When setting the call up, you can combine many of the constants together to
get what you want.
For example, to only allow the opening of multiple existing files, you might
pass 
OFN_FILEMUSTEXIST and OFN_ALLOWMULTISELECT to the function call.

Bobby

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Sunday, August 17, 2003 8:53 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] SysCmd constant conflict


Thanks for the info -- learned something new today.

> >Other constants don't work like this.
>
> Many do.

======I don't suppose anyone could identify the others or can I just assume
that any enum where the members could be applied at the same time will
behave this way?

Susan H.

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com