OK - part of the code in the system pulls data from MS SQL. So - I was trying to mod this code - to add NULL as an option into the Select. But, I suspect I'm not doing it correctly. Was looking around in online help - but, could not quickly find the answer. So - I took a shot at trying to implement this. This is only Part of the line of code - but, you can see the attempt to define NULL: SELECT d.secid ,d.sec_name AS sec_nam ,d.coi AS issue_cnty , t.taxrate_el NULL FROM [dbo].[Dividends] as d JOIN [dbo].[Trandata] as t ON t.dividend_id = d.dividend_id
Any further input would be greatly appreciated.
Regards, Kurt Wendt Senior Systems Analyst
Tel. +1-212-747-9100 www.GlobeTax.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Dave Thayer Sent: Tuesday, June 14, 2016 5:16 PM To: profoxtech@leafe.com Subject: Re: A Blank Value for a Number?
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 Kurt_Wendt@globetax.com 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
[excessive quoting removed by server]