Forum Discussion
Migrating Access back end to the cloud
- Do you want to run this relational database application as a web - browser based application, or as a desktop application?
I don't know which "guys in India" you mean, or what they recommend, but you really don't need a lot of other software packages if you are going to continue to use this as a desktop application. However, if you want to replace the Access interface with one that will operate in a web browser, you WILL have to invest in and learn to use the appropriate tools for that.
So, start by explaining who will actually use it, where they are physically located (in a single facility or dispersed among several) and how you anticipate using this relational database application. From there, we can examine some options.
George Hepworth Thank you. You'e being incredibly patient and generous of your time.
The first catch was that I've been using unblock.us to give me access to UK TV. It had loaded a different IP address into the portal. I've removed unblock.us and restarted the computer and the client address shown in portal.azure now conforms to the ip address returned by my whatsmyip.org. The same ip address has also been added as a rule along with a range from xx.0.0.0 to xx.192.192.192 that includes my ip address. Since neither I nor my users will have a fixed ip address, I'll have to come back to that later.
I've checked that the version of SQL Server Migration Assistant that I have is v8.6 and I've started a new project. I've done this so many times I'm now on to SqlMigration9! In the top left hand panel, I'm able to select the folder in which my Access back-end resides. When I click "Connect to Azure SQL Database" and enter my password, I get a connection string, which seems encouraging. In the top left panel I can select either Tables or Queries or both. I selected Tables as the queries are all in the front-end. But I see that, when I hover over the name of the database (CorallDataAzure) I get an error message relating to the COM class factory! I'm certainly running 64bit Windows, 64bit Access and, since the Migration Assistant .exe file resides in the Program Files folder, I assume it is also 64bit.
So I fear I may have hit the buffers again.
Kind regards
Graham Cresswell
Ah, yes, there is, or was, a problem with regard to 64 bit Access. I don't have the reference off the top of my head, but it involves downloading and installing the proper bits. I'll go look for the discussion.
Many thanks. George Hepworth That seems to imply that, since I am using Access 365 as a part of Office 365, it should work "out of the box".