Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
New SQL Server Records NOT FOUND!
Message
From
18/05/2018 23:20:09
 
General information
Forum:
Visual FoxPro
Category:
Client/server
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 10
Network:
Windows Server 2012 R2
Database:
MS SQL Server
Miscellaneous
Thread ID:
01660006
Message ID:
01660141
Views:
91
>Tamar,
>
>Of course, you were right! The VFP Select on the RV did not retrieve the new rec BUT the SQLEXEC() did! I don't think the filter was the problem.
>
>The new record created seems to put NULLS in blank fields and the Logical/Bit is BLANK when the converted data has "False" in it. When I manually entered 'False' in SSMS in all Logical fields the record was retrieved. VFP must have an issue with this.
>
>The Promatrix Framework does the insert record. Any ideas about the NULL issue and the Logicals? I didn't realize that could be an issue. Still not 100% sure about it but I think I'm on the right track.
>
>Thanks much.
>
>Bill
>
>UPDATE: I found that the Filter fields that had NULL when created may be the problem, maybe not the Logicals. Everytime I reference a character filed with a NUL there is an issue. Must make Char NOT NULL. I must keep testing!


VFP defaults new numeric columns, for example to zero. SQL server defaults them to NULL
One way to eliminate NULL's (I hate them) is to put default values in each column of the SQL table.
That's really kludgy, but it will work.
Your framework should be handling this for you, but apparently it doesn't.
Anyone who does not go overboard- deserves to.
Malcolm Forbes, Sr.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform