>>>I heard it was a VB/Access problem, or a VFP - SQL Server soultion that used remote views rather than stored procedures :).
>>
>>I'd put the blame on the VB'r. VFP programmers never make mistakes.
>
>Only when we are drinking too much beer in Milwuakee :).

Isn't that supposed to be Milwaukee? You are not giving a good example...