Preserving Access Application During SQL Server Reboots

[W]

We have a Microsoft Access application that terminates with an error every
time SQL Server is restarted. My understanding from Googling this is that
either the application or the driver is using database queries / connections
that become invalid as soon as SQL Server stops. Is there any driver we
can use with Access that would implement a connection pool or some mechanism
behind the scenes that would allow Access to survive an SQL Server reboot?

[Erland Sommarskog]

Post by W
We have a Microsoft Access application that terminates with an error
every time SQL Server is restarted. My understanding from Googling
this is that either the application or the driver is using database
queries / connections that become invalid as soon as SQL Server stops.
Is there any driver we can use with Access that would implement a
connection pool or some mechanism behind the scenes that would allow
Access to survive an SQL Server reboot?

Sounds like a question that is suitable for an Access forum.