Hi Kevin,

Is that convenient for you just to put the login call right into Data Retreival method as the first line on condition you are running it from the development environment?
Something like:

***
IF _VFP.StartMode = 0 && from the development environment
cLoginString = oSecurity.Login(cName, cPassword)
* ... more checks here
ENDIF

*Run the actual method code here depending on login result

>I have various COM DLL's created in VFP.
>
>Security procs
>Registry procs
>INI File procs
>Data Access procs
>General Procs
>Error Handler
>
>The question is this:
>I'd like to make it necessary for developer at the Command Windows to
>Login through the security DLL before access to the Data DLL is allowed.
>
>Obviously I can control this inside an application, but how would I prevent access to
>a Data Retreival method in the Command Window unless a valid login has been done?
>
>I had thought of the following:
>
>

>
>** Step 1
>oSecurity = CREATEOBJECT("Security.procs")
>cLoginString = oSecurity.Login(cName, cPassword)
>
>** At this point, cLoginString contains a unique string returned
>** by the Login function
>
>
>
>** Step 2
>oData = CREATEOBJECT("Data.procs")
>oData.cLoginString = cLoginString
>oRecordSet = oData.getSomeData(cSqlCommand)
>
>

>
>
>The problem here is that there is nothing stopping someone from simply
>saving the string to the clipboard, and accessing the Data DLL from the
>command window at any time.
>
>Any ideas?
>Many Thanks