Re: Using a Database within Windows + Dyalog APL

AAsk <AA2e72E@[EMAIL PROTECTED]
> wrote in news:95095073-5d69-4a27-a70c-
a6f13752299f@[EMAIL PROTECTED]
> [... deleted ...]

A lot of people use APL because it offers a programming model which is 
simpler and more effective than "real programming".  I think if I had to
do 
all this I'd just give up and do something interesting instead.

> 
> My preferred approach would be as follows:
> 
> 1. Write a COM component using C# (also possible with VB6.0). I guess
> you can emulate this with a namespace.
> 
> 2. The COM should allow clients to choose for alternative databases
> i.e SQL Express or Oracle or DB2 etc.
> 
> 3. Keep the COM simple & robust and secure.
> 
> a. The COM should take a property - which provider's database to use.
> b. It should provide a method, say ExecuteQuery, that returns a
> recordset i.e. DQL.
> c. It should provide a method, say, ExecuteNonQuery that does not
> return a recordset i.e DML etc.
> d. Connect to the database using a UID & PWN stores in the Registry,
> encrypted.
> e. User logins should be managed by your application code-details can
> be stored in a table in the database.
> 
> [... deleted ...]