David McAfee
davidmcafee at gmail.com
Wed Dec 21 12:12:00 CST 2011
A coworker wrote a new stored procedure that works just fine when ran from SSMS. If either of these are ran from SSMS: EXEC stpR6Payouts '1/1/2011','11/30/2011','' EXEC stpR6Payouts '1/1/2011','11/30/2011',NULL The data is returned as expected. If, the sproc is ran from VBA, or directly through the immediate window, we get different results. The sproc run from Access will return a few rows short, and data is being calculated incorrectly on the rows that are returned. Hit F5 in Access, and a different row count (and data on the returned rows) will be different. I've always assumed SQL was doing all the work and returning a resultset to Access, but it doesn't appear this is actually what happens. Does anyone have any ideas? TIA, David