Commasense, what exactly is the problem you are having? Do you not have the install key for the Office 2010 you are using now? Do you still have access to the computer that office 2010 is installed on?
Because if so, it is straightforward to fix. You have already paid for office 2010, and Microsoft allows you to have it installed on one computer at a time. So you do this :
a. Get the product key from the computer it is on with this tool.
b. Uninstall office 2010 from the computer it is on
c. Install office 2010 on your new windows 10 PC
d. Make sure to set up proper backups! I suggest an automated solution like backblaze or mozy. Every computer and HDD will eventually fail. (admittedly in some cases it may go obsolete first but still)
Now, a lot of the posters here, myself included, think maybe you should consider using newer tools, but hey, this’ll work.
Well that hardly helps. Even if you no longer can access the computer in question, did you buy Office in a box? Did you buy it via their web-store? If it was a box, there is a sticker on the DVD or case. If it was from their web store, there will be an email that has the key. That’s all you need.
If you pirated it…well…you wouldn’t even have this problem, because you could just pirate it again.
In my experience, Microsoft Access databases traverse versions between 2010 to 2016 much better than the transition between versions from 97 to 2007. Converting from 97 to 2000 and from 2000 to 2007/2010 was a major headache, I recall.
If your database is already in .accdb format, there’s a good chance it will work in 2013 or 2016 without much fuss. It does depend on what you’re doing in the VBA code though, because some bits of the language were dropped or changed across the years.
If you hated the introduction of the ribbon (I know I did - it took me years to accept it), you might actually like later versions of Office - the ribbon is still there, but it has got a lot more menu-y and is now more similar to the original File/Edit/etc style of menus than ever.
a. Old computers suck power. Replacing them with cheap newer computers will save their own cost in power over a few years.
b. If you want to surf the net, it isn’t the OS that’s causing the slowdown. Ubuntu won’t be any faster running google chrome or firefox. It’s the demand from the web browser itself.
So what you would have to do to make these computers not suck is either upgrade the ram and install an SSD (if they aren’t that old, that’s all they need) or replace them with a very inexpensive and tiny computer that is faster.
IME as an IT professional they want to adhere to a standard or have guaranteed compatibility with other people running the same software. For example, macros can be exceedingly twitchy between versions. More prosaically, it can be written procedures that are the sticking point. Click this, select that, click the other… You can’t guarantee that they work the same way between versions.
Or, it’s just because that’s what they’re used to.
