I don't know what else to say aside from if it's saying incorrect password you've got an incorrect password. Try resetting the password on the server to something else and make sure you got the right one. There's really only one thing that could give you that error message and that's an incorrect password.

It appears maybe in the rs call. I am fixing that now. The database opens and I can access the tables, but it is in the protection process up front.

Wow, finally found it. In the PassThruQ I was calling a "BlockT", one of my tables. This failed every time.  I switched the PassthruQ to "VendorT" and then it worked every time. This fixed all the other issues.  I have no idea why BlockT did not work. I can look at it in Access ok, same as VendorT, but it does not work in the PassthruQ. "Select * from BlockT" vs "Select * from VendorT. Not an easy fix to find.

Is BlockT on the Server or is it a Local Table?

Both tables are on the SQL server.  Same database, same password.  Just Odd.

Figured it out. We have 20 different models for design of retaining walls.  In the SQL Server we name the tables based on their specific vendor: i.e. dbo.ALBK_BlockT, or dbo.KYSTN_BlockT etc. In ACCESS we rename it to BlockT for each unit we design with (so 5 tables: BlockT, Block_TypeT, ConnectionShearT are product specific, VendorT and GeogridT are not specific.) and thus we have 20+ different Access database. The reason VendorT and GeogridT work are they are dbo.VendorT and dbo.GeogridT.  We have another program written in C# to access the data and there we add the label in the code: dbo. & vendor & _BlockT.

I should have thought of that sooner instead of hours digging through why the code would not work. A simple fix now.  Thanks for the ideas. Really appreciate your training Richard, the concepts and examples are a real help.

Yep, that'll do it. I remember having a similar issue when I first started learning SQL Server.