I realize that MSAccess/VBA is a single-threaded application. But, maybe a silly question, can I call an SQL Stored Procedure from MSAccess and let the SQL Server do the heavy lifting in parallel with other MSAccess tasks?
This is my current SP call, takes about 4 minutes (no progress indicator at all) to complete with my largest datasets (exports data from SQL, reformats to produce proper CSV format, ZIPs and puts to my FTP Site - reformatting is the longest task, export & FTP are very fast):
Set cnn = New ADODB.Connection
cnn.CursorLocation = adUseClient
cnn.ConnectionString = "driver={SQL Server};server=" & TempVars!my_ip & ";Trusted_Connection=no;Database=" & TempVars!my_Database & ";UID=userid;PWD=password"
cnn.CommandTimeout = 0
cnn.Open
strSQL = "ExportToCSVZip 'ITEM', 'InvId', '4892', '\\123.456.789.147\Processing\Exports\', 'ProdCIV', 'Y';"
Set rs = cnn.Execute(strSQL)
Am I locked into waiting for this long external process to complete before continuing in MSAccess?