FIXED: INSERT INTO when a string starts with "NULL"

[Ruslan Zasukhin]

on 4/17/03 3:55, Steve Kellogg at stevekellogg at mezzotechnologies.com wrote:

> Hello Ruslan. 
> 
> I've hit a brick wall that I hope you can help me with.
> 
> I've spent the last 4 days converting my entire app over to user cursors
> instead of the BaseObject access that we've been using for the past two years.
> 
> Now I find that adding records with  INSERT INTO (I'm using a BIND array) has
> a little quirk that I didn't expect:  If I try to insert a text value THAT
> BEGINS WITH "NULL", you're interpreting that as as NULL VALUE instead of a
> TEXT value that begins with NULL.
> 
> I've included 2 databases that illustrate this in case you need them, but it's
> fairly straight forward.
> 
> To see the problem, look at the "NAME" field of the "TARGETS" table.
> 
> The BEFORE database includes a folder named NULL12345.
> 
> You'll see that the AFTER database has a folder named "" where the "NULL12345"
> should be. 
> 
> 
> I was hoping not to run into any GOTCHAS on this conversion, because we're set
> to release our OS X version this week, and now I can't do it until this is
> fixed. 
> 
> Is there any quick workaround that you know about?

Hi Steve,

Sorry for delay.

FIXED.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------