I've only done this with cursors, I'd probably want to make a temp read/write cursor intermediate just as an intermediate before excel export, this can also save you from accidentally polluting other dataflows with unwanted null values.
I have one project where I can do this with cursors defined with a CREATE CURSOR command with nulls explicitly allowed, and with cursors generated from SQL Pass through. I don't know if VFP is clever enough to only allow nulls on cursors made by SQL Select To...Curser cFoo READWRITE depending on the source table definition though. On Tue, Jun 14, 2016 at 2:48 PM, Kurt Wendt <[email protected]> wrote: > Really?? > > OK - here's the quick test I did. I took an existing DBF file, copied a > couple records to a new Dummy.dbf. > One of the fields was Numeric 5 0 > Then - I simply went to one of the records and ran the following command: > REPLACE errline WITH .NULL. > > VFP then reports back - Field Errline does not accept null values. > > Hmm... > > Regards, -- Dave Thayer Denver, CO _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/caao+qoxkhocjjvxdohcvbs5zolxdu71372qz52ekxudppxo...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
