SqlSelect doesnt wanna work

[Vansh Singh]

Ruslan,

I figured it out. What was happening is that it was indeed talking to
the database but when I did an 'alert' to see the value, it didn't
realize that it was a string that I was trying to look at. So instead of
just doing "alert(sys_col[1])" , I had to do this to force it to treat
sys_col[1] as a string:

Alert(EMPTY & sys_col[1])

And that works! I don't know why the alert wouldn't treat it as string
right off the bat but oh well... problem solved.

Thanks for your help.

Regards,
Vansh

-----Original Message-----
From: valentina-bounces at lists.macserve.net
[mailto:valentina-bounces at lists.macserve.net] On Behalf Of Ruslan
Zasukhin
Sent: Saturday, January 31, 2009 1:28 AM
To: valentina at lists.macserve.net; Kirill Pekarov
Subject: Re: SqlSelect doesnt wanna work

On 1/31/09 12:39 AM, "Vansh Singh" <vsingh at us.counterp.com> wrote:

Hi Vansh, 

> I thought so too but when I looked at an example under
> Common\Database_CreateCloseOpen\, it said:
>   
> -- Turn on logging.
> Valentina.debugLevel = #kLogNothing
> 
> That apparently only turns it on and doesn't log anything. Noted.
> 
> 
> So I put in #kLogParams and I still don't see a V4MD_log.txt anywhere

If you project is small, do not depend on other Xtras
    you can compress it and send to Kirill for fast check
    see above CC for his email

-- 
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]


_______________________________________________
Valentina mailing list
Valentina at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina