Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
New SQL Server Records NOT FOUND!
Message
From
17/05/2018 18:09:40
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
 
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:
01660073
Views:
90
If you're sure you're inserting into the same database as you're querying, then the WHERE clause has some characteristic that's not met by the new records. We can't guess from afar what it is- sorry! However, earlier advice re pulling records in Management Studio and compare found vs not found records, and reviewing profiler, may give you an "aha!" moment especially if you focus on what's in your WHERE.

Re adding records: dbfs add records sequentially, so if you do an unordered query you can expect results in the order added. Whereas in SQL Server, an unordered query is literally in no particular order. You could order by your identity field if you need them in the order added.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us.
"
-- Shakespeare: Coriolanus, Act 1, scene 1
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform