I am trying to find out if it's feasible to use temporary and local objects (in this specific case, a temporary local table) with Access being involved as front-end clients. I'm trying to do some data processing on server side, with Access feeding the inputs, which ultimately will return a recordset but this requires several steps along the way.
I know that Access may create more than one session during the application lifetime with the SQL Server, so the local temporary tables may go out of scope if it's left idle, for instance. Would it be remedied by holding a persistent ADO connection, or can session change even with the same connection object?
Thanks for any guidance.
I know that Access may create more than one session during the application lifetime with the SQL Server, so the local temporary tables may go out of scope if it's left idle, for instance. Would it be remedied by holding a persistent ADO connection, or can session change even with the same connection object?
Thanks for any guidance.