Access database cannot be accessed from new laptop (Windows 11), only from old one (Windows10)

[AKAnalyst]

Hello,

I have been accessing a database successfully from a laptop with Windows 10. I can still access it from that laptop, but a new laptop (with Windows 11) returns the following error code(s) when I try to access the same database, using the same front end/ autoexec file:

"There was an error in quering the data. 3151, ODBC--connection to 'SQL Server Native Client 11.0 [database name], 1433' failed. SELECT Current_User as UserName"



When I click OK, the following error message then appears:
"There was an error connecting to the database. 91, Object variable or With block variable not set".

After clicking OK, I then get another error message very similar to the first one above. After clicking OK again, the final error message is "Run-time error '91': Object variable or With block variable not set."

I am not personally well-versed in VBA or the inner workings of Access. I'm hoping someone can help explain these error messages, and suggest how I can access the database from the new laptop.

Thank you!

[Gicu]

A few things jump out:
-looks like the front-end is connected to a SQL Server back-end; have you ensured that the back-end SQL database is accessible from the new laptop?
-besides the Access front-end itself you need to install the same SQL Server driver on this new laptop, the one mentioned in the error: SQL Server Native Client 11.0 (note that this is a fairly old one and you should consider upgrading to the lates SQL driver - it will involve changes to the VBA in front-end most likely unless you have a local SettingTable)
-have you enabled to Trusted Locations for the front-end on this new laptop to ensure the VBA runs unencumbered?
Cheers,

[ArviLaanemets]

Also yoou have to check, how is the connection to BE defined in your FE. In case an ODBC connection defined in your old computer is used instead defining the connection directly in FE, you must create the this ODBC connection in new laptop too (or redesign the FE).

[AKAnalyst]

A few things jump out:
-looks like the front-end is connected to a SQL Server back-end; have you ensured that the back-end SQL database is accessible from the new laptop?
-besides the Access front-end itself you need to install the same SQL Server driver on this new laptop, the one mentioned in the error: SQL Server Native Client 11.0 (note that this is a fairly old one and you should consider upgrading to the lates SQL driver - it will involve changes to the VBA in front-end most likely unless you have a local SettingTable)
-have you enabled to Trusted Locations for the front-end on this new laptop to ensure the VBA runs unencumbered?
Cheers,

Thank you very much for this Vlad! Due to my ignorance, I need to ask:
1) How do I ensure that the BE SQL database is accessible from the laptop?
2) In "trusted locations", how do I specify "the front end"?


Thanks for your help!

[AKAnalyst]

Also yoou have to check, how is the connection to BE defined in your FE. In case an ODBC connection defined in your old computer is used instead defining the connection directly in FE, you must create the this ODBC connection in new laptop too (or redesign the FE).

Thank you for this! Might you be able to tell me how to create an ODBC connection in the new laptop?

Cheers!

[Gicu]

Usually if the new laptop is on the same network with the old and has the same permissions it should be able to connect to the SQL server db. Have you installed the Native Client 11.0 driver? As for the trusted locations you need to go to (on the Access main ribbon in the front-end) File\Options\Trust Center\Trust Center Settings\Trusted Locations\Add Trusted Location and browse for the location of the front-end you are in-you'll need to check the Allow Trusted Locations on the Network if the front-end is not on the C:\ drive (which it should).

Cheers,

[ArviLaanemets]

Thank you for this! Might you be able to tell me how to create an ODBC connection in the new laptop?

Windows Administrative Tools>ODBC Data Sources (there you can select between 32 and 64 bit versions).
Look at your old comp at first, and when there is the connection defined, create it for new comp too (with same name) Or export it, and imoprt it into new comp. When in old comp no connection exist, then look for other solutions.