Please help with API way of checking UserID and Password

[Barry G. Sumpter]

Hi Ruslan,
Thanks for taking the time to reply.


Oh sure, now ye tells me!  ;-P


Especially, now that I've finish all the testing 
and now looking thru doco to Research the security issues 
regarding opening a port on my 
Personal computer here at home 
So I can access my vServer 
thru lcServer 
on IIS 5.1 
via the WWW 
from my Android.
It works.  
I've removed the port forwarding until I finish more security research.


Actually, now that you mention it,
I'm thinking since my vServer and its .vdb and the lcServer are all 
on the same personal computer here at home,

then it's not really remote but could be considered local.
I'm happy with that statement but it should probably be a question.  =|

Since I am using the API way.  Is that the best way to narrow down the
dataset?
i.e. find field into dataset1, then find field based on dataset1 into
dataset 2?

Now that it's finished there doesn't seem to be that much in it.
So if ya tells me its better with SQL I might have a go.

But it's a tossup between that and testing vServer 5
Hmmmmmmmmm   ;-)


------------------------------

Message: 3
Date: Wed, 28 Mar 2012 09:10:02 +0300
From: Ruslan Zasukhin <ruslan_zasukhin at valentina-db.com>
To: "valentina at lists.macserve.net" <valentina at lists.macserve.net>
Subject: Re: Please help with API way of checking UserID and Password
Message-ID: <CB9885EA.FD093%ruslan_zasukhin at valentina-db.com>
Content-Type: text/plain;	charset="ISO-8859-1"

On 3/27/12 6:18 PM, "william humphrey" <bill at bluewatermaritime.com> wrote:

> It is never a distraction. There is so few places to learn about using 
> Valentina with Livecode.
> 
> On Mon, Mar 26, 2012 at 7:10 PM, Barry G. Sumpter 
> <barrysum at bigpond.net.au>
> wrote:
> LOL.
> Every time I post I find a solution in 5 mins afterwards.
> 
> The very next example in the Field Find allow us to nominate a dataset
> (set1) to perform the Find Field on.
> 
>  ? put VField_FindValue( fld_string, "aa", set1 ) into res

Hi Barry,

I see you try to use API Way for Livecode. But why?


IMO for Livecode more simple to use SQL.

I'd say everybody should tend use SQL even if you work with local db ..

Only hot places, which you need made faster can be overriden with API style
...

Why better tend to use SQL?
Because then your local app can be EASY converted into client-server app,
which works with remote server in other city.

API Way is perfect for local dbs, but can be much slower for remote
servers...



--
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information http://www.paradigmasoft.com

[I feel the need: the need for speed]