I know the field. Its the endtm field. It is all numbers even though its being stored as varchar. The weird part is if gather all the data...

Thank you for the response. That does somewhat make sense. But I have still been researching as well and haven't come across any other explanations.

We actually use Confio's Ignite when I am looking at resources. I have attached a screenshot. The affinity is set to the defaults. No virtuals and no performance...

I was able to figure it out with the inscope function

If I don't use the top 400 I will get way too many records back. The table has millions of records

Its running over vpn to the customers server from our datacenter.

I tried delaying the validation and still getting the same error.

The driver is installed on the server. I tried the 32 bit vs the 64 bit. Neither of those seem to be the issue

That's not a bad idea to find differences between objects. I'm concerned also about differences in stored procs but that is not as much of an issue.

Thank you so much. that was a good catch.

Apparently I can't read. Can you please tell me what I have misspelled?

Thanks!! That may be the best way to fix it. Or a variation at least.

Thats worth a shot. I'll do some testing. Thanks

How do you determine the Context_info? I don't understand how I could use that to avoid the trigger?

That would be ideal. The problem is there are many places that update or insert into the patient table. And no one can tell me all the places....