Robert L. Stewart
rl_stewart at highstream.net
Wed Dec 6 15:02:23 CST 2006
Well, that works and does not work. It kills the stored procedure if we close the connection. Any one with any ideas? At 12:00 PM 12/6/2006, you wrote: >Date: Tue, 05 Dec 2006 14:01:30 -0600 >From: "Robert L. Stewart" <rl_stewart at highstream.net> >Subject: Re: [AccessD] ADO Stored Procedure Call >To: accessd at databaseadvisors.com >Message-ID: <200612052005.kB5K5Kq20980 at databaseadvisors.com> >Content-Type: text/plain; charset="us-ascii"; format=flowed > >No, we are running through terminal services and to different databases. >It has to go through ADO. I think I found it, but waiting on the boss >to do the testing. Asynchronous mode on the connection open in ADO is >supposed to allow you to close the connection and the procedure to >continue to run. > >At 12:00 PM 12/5/2006, you wrote: > >Message: 3 > >Date: Tue, 5 Dec 2006 06:41:52 -0800 (PST) > >From: Lonnie Johnson <prodevmg at yahoo.com> > >Subject: Re: [AccessD] ADO Stored Procedure Call > >To: Access Developers discussion and problem solving > > <accessd at databaseadvisors.com> > >Message-ID: <20061205144152.19599.qmail at web33103.mail.mud.yahoo.com> > >Content-Type: text/plain; charset=ascii > > > >I know this sounds simple but could you call your stored proc via a > >passthough query in your code? > >