SimonxMills
New member
- Local time
- Today, 13:38
- Joined
- Sep 20, 2005
- Messages
- 1
Hello all. Im looking for some help please
I currently have a module that uses adodb commands to run sone stored sql proceedures. As we update from access to sql slowly (time constraints and lack of resource dictating the migration pace unfortunately) i have more and more reliance on this connection type.
I now have a stored proc that takes 20+ plus mins to run, so im looking to start the proc using the adodb command, but then move on without waiting for the confirmation its finished. I will then reference the admin table that the proc writes to as it goes on at various points of my access vba for confirmation the proc is complete. Currently such big procs cause crashes and/or delays.
Can anyone help me/tell me if this is possible please. I have set timeout to 0 to try and prevent the connection stopping, but i want access to use the 'dead time' whilst sql runs to quiken my whole process up.
I currently have a module that uses adodb commands to run sone stored sql proceedures. As we update from access to sql slowly (time constraints and lack of resource dictating the migration pace unfortunately) i have more and more reliance on this connection type.
I now have a stored proc that takes 20+ plus mins to run, so im looking to start the proc using the adodb command, but then move on without waiting for the confirmation its finished. I will then reference the admin table that the proc writes to as it goes on at various points of my access vba for confirmation the proc is complete. Currently such big procs cause crashes and/or delays.
Can anyone help me/tell me if this is possible please. I have set timeout to 0 to try and prevent the connection stopping, but i want access to use the 'dead time' whilst sql runs to quiken my whole process up.