Obtaining Access 2010

[GBalcom]

So, I just updated to a newer computer. This computer has Access 2013, my old one has 2010. I have some FMS add in's for access 2010 that I've been very happy with, and I'm missing them in 2013. Also, I seem to prefer the 2010 version for my desktop applications.

Is there anyway to obtain an older license from Microsoft if you have a valid current license?

 

[Ranman256]

the license goes with the Version. sorry.

 

[Gasman]

Are you not able to uninstall from an old computer and install to a new computer with Office?

I *thought* that was allowed, and was the reason people sold keys on ebay, which worked.?

 

[GBalcom]

Well, I called Microsoft....and after 20 minutes of my life past, and talking with 5 different people, I ended with the same result. No way to get a 2010 version. They suggested I find a retailer that still sold it...However, I've also heard they "request" the old versions back from retailers....it seems I'm out of luck.

 

[JLCantara]

@RanMan: not sure MS cancelled my A2007 license.

@Poooooor GBalcom, you got screwed by MS (so I did). You will find that A2013 doesn't support automation, Activex controls and events of reports. Actualy, MS his imposing PowerPoint DB and will gradually force people to move to it. On top of it they avoid talking about what you LOOSE doing so.

Good luck, JLC.

 

[burrina]

I have a copy of Access 2010 and Microsoft can try and get it from my cold dead hands!
I will NOT be upgrading. Suggest you go on Ebay and search.

 

[JLCantara]

To further prove MS bad faith, consult
Should I create an Access app or an Access desktop database?
when creating a new desktop app.

1 - Your organization is not using SharePoint or your Office 365 plan does not include SharePoint Online. Even with PowerPoint, you still can create desktop app.

2 - You want complete control over the look and feel of the database user experience. But you can't use Activex controls...

3 - You're willing to make sure each database user either has Access or has installed the Access runtime. The installation package will auto. take care of RT Access.

4 - Everyone can connect to the computer on which the Access database is stored, and will most likely use the database from a networked desktop or laptop computer. Not necessarily true: one can still (for now) use remote connection.

5 - You’re willing to redistribute the database front end every time you make a design change. That's no problem: it has been amply discussed in this forum.

6 - You have people creating and modifying databases who are using different versions of Access. Still true with Web versions - I had A2007 running with A2013. But no lower version can access upper version app.

Good day, JLC.

P.S. - I think we should get organized and do something bold about it: MS would hate to be accused of cheating. Don't forget, it's big business in there...

 

[pbaldy]

You will find that A2013 doesn't support automation

Do you have more info on this? I recently ran into a problem where Outlook automation wasn't working. I was suspecting a Win 8.1 issue, but the user had Outlook 2013 and the Access 2013 runtime.

 

[JLCantara]

@Paul: Oh yes I do.

I tested this:

Dim app As Access.Application

Set app = New Access.Application
app.OpenCurrentDatabase ("C:\Users\JLCantara\Desktop\Nutrition\Système\NutriSys\NutriSys.AccDB")

The app exists and is part of a big nutrition system. I get error 7866: checked on the web, replies to this issue should be used for a book about vba programming insanities...

What is funny is the following

Dim app As new Access.Application

Set app = Access.Application
app.OpenCurrentDatabase ("C:\Users\JLCantara\Desktop\Nutrition\Système\NutriSys\NutriSys.AccDB")

I get 7867!!! This means that the 2 equivalent statements are not equivalent. It seems that Access is such a mess that the development team "s'enfarge dans ses lacets" (sorry for the Québec French...).

Now do I need to say that my previous version of A2013 was French (stupid error) and was giving a totally different error.

A2013 is a mess and no one should switch from A2007/A2010 to A2013.

 

[GBalcom]

Not sure I understand the "doesn't support automation" part. But I can tell you just yesterday I was working in VBA and making access copy and rename a master excel (.xls) spreadsheet, then opening it and population certain ranges with data. And this was with Access 2013...

 

[JLCantara]

Were you using Office 365 Personal?

 

[spikepl]

To be honest I'd be much more careful with sweeping statements like yours, especially here, because many people read the posts, and might take it as gospel.

I have not been able to locate any information on the web whatsoever to support your contention that A2013 does not support automation. That is not proof as such, but no comparison of new or deprecated features mentions this, in any connection with any A2013.

 

[JLCantara]

Well, did you read post #9? Do you want screen shuts of what I say?

The problem is definitely with, at least, Office 365 Personal's version of Access. Balcom can perform automation but didn't answer yet as what version, package, etc. he is using.

 

[spikepl]

I'm not blind. Not yet, anyway. Unfortunately you subvert your own credibility by complaining about two different errors generated by in fact two different circumstances.

 

[JLCantara]

OK Spike you have the last word. Case closed!!!!

 

[speakers_86]

I tried 2010 and thought it was bad. MS got it right with 2007. Since then, they just change things to make a new product. See my signature.