Recent content by Charax

Thanks for note, Pat. Your installation sequence makes me think that perhaps Windows 11 has the missing drivers. With SSMA installed on my backup computer, I'm going to leave well enough alone. I didn't mind deleting and reinstalling Office 2019 on the backup machine so I could try the Access...

Pat, do you have both Access and Access 2016 Runtime installed on same machine? For me, unfortunately, installing SSMA 32-bit was not possible on three of my Win 10 (64-bit) computers. One is a new Dell tower but I continue using Win 10. After many frustrating hours and multiple attempts, the...

Thanks for your note, Pat. It is my experience that, if you have an O365 installed version of Access, you cannot install Access 2016 Runtime. Trying to do so causes the We found a problem! error (above). Apparently, to install SSMA, you must have one or more drivers installed by Access 2016...

I just resolved a somewhat similar problem that required deleting Office, installing Access 2016 Runtime, deleting Runtime, reinstalling Office. Very clunky, brute force. But maybe gives you ideas at my thread on Error Installing SSMA. (Sorry, don't know how to link threads yet.)

Thanks for your note. Currently I'm running SQL Server Dev as BE on local PC with simple linking from Access FE. But I have a legacy (1990s) Access FE/BE that the customer wants to have SQL web served. I'm currently looking at how to handle that one. I'll be watching for tips from you too.

So, I think I now understand why SSMA would work on my computer once I saw the following error message: It popped when I attempted to install the Access 2016 Runtime (32-bit) while I had Microsoft Office 2019 Pro MSO. Numerous Google search references mentioned to the need to install the...

Pat, is there a way to check 32-bitnesss for SSMA? On the download page there are now two choices, SSMAforAccess_10.2.25135.msi OR SSMAforAccess_10.2.25135_x86.msi My Office is 2019 Pro 32-bit. To install SSMA, I used filename SSMAforAccess_10.1.0_x86.msi (downloaded several days ago). Maybe I...

Good idea so thanks, theDBguy. I created a simple, totally fresh ACCDB database in Access 2019 with multiple tables, some queries, relationships. I set the General Settings default file format for Blank Database to Access 2007-2016. Alas, an attempted SSMA conversion of the virgin database to...

Thanks for a thoughtful suggestion. I saved the legacy MDB file as ACCDB and received message that it was converted to Access 2007 format: However, when I ran SSMA, the same identical errors popped as with an MDB file.

I installed file SSMAforAccess_10.1.0_x86.msi; I accepted the recommended upgrade to v.10.2 during installation. The installation ran smoothly, My computer has Microsoft Access 2019 MSO (Version 2505 Build 16.0.18827.20102) 32-bit on Windows 10 Pro I also have SQL Server 2019 (RTM) -...

I'm an Access programmer who joined this forum in 2012. I began using Access in the 1990s and continue today with Access as a front end application to SQL Server. I've visited this forum many times over the years, fixing bugs and learning from those truly expert in programming. I've tried to...