You up to talk shop? I’m staring down the barrel of a similar task I’ve been putting off until I have a puzzle mood type of day. But also worried about doing it well because there’s definitely more. How do you usually start to approach migrating legacy systems?
Access SQL is just slightly different syntax to what I know, I can usually translate but it’s slow because it’s all one big block. I started by using PowerShell to dump all the objects and query text into Excel so I could find all the connections. Some broken down at some point so half the data is on the server. This thing serves as kind of like an ETL tool and they have two access DBs for front and back end seems like, using data from server, file system, local access tables. There’s a bit of looks like VBA in there too propping up the forms.
What thread do you pull first to unravel the Gordian knot? Access is a bit out of my wheel house. Bravo to the cowboy business users who were able to get the job done, but it’s hard for me to parse and of course they are retired so no SME to speak of.
Lend me your wisdom, please.
Yes this is tremendously helpful! The syntax highlighting alone is going to make this much easier. I totally overlooked this, but it’s clearly a winner. Even just having the vocabulary for a few of these things feels like an incoming boost.
We are big on Microsoft too, so power BI and power apps is the destination. I’m coming around to these tools, if nothing else it gives some visibility so they can’t loom in the shadows like these Access leviathans.
Really appreciate the time, and on the weekend no less. Have a great one.