>>I'm not familiar with ProMatrix. However, I wonder if it's some sort of security issue.
>
>>If the app or the framework have user access or privilege control (i.e. users start by entering a user name and password), maybe new records are being added in the context of a different user, and are being filtered out by default in your app, or in the framework.
>
>>If you have an "administrator" logon for your app, do you see the issue if you use that account?
>
>Thanks for your input Al.
>
>It's definitely not a security issue in my framework. Been using Promatrix awhile and there is not a filter on users concerning adding records. I am signed in as an Administrator anyway.

Others have probably said this, but as far as SQL Server is concerned, the query results you get using SSMS are definitive. If new rows show up there, then they do exist in SQL Server, no ifs, ands or buts.

If those new rows do NOT appear in your app, then it's an issue with your app, not SQL Server. Your app must be filtering on some unexpected column(s).

I see two approaches:

1. Investigate how ProMatrix queries "remote" data sources. If you're experienced with PM this is probably the easiest approach

2. Very closely compare new rows that don't show up vs old rows that do in SSMS, and work backwards from any differences found