office 2013 and 365

Hi EE
I have a minor irritant. I am using office2013 for the first time. I create an mde then use Innosetup to install. All the PC’s have Windows 8 and office 365, Windows 64 bit and Office 32 bit.
 I have installed so far on three PC’s two successful  and one unsuccessful. The unsuccessful one gave me a message “You are using an older format etc”. To get it working I opened 2013 and recompiled into and mde on that pc and now it’s working ok.  I have a number of PC’s to install but would like to figure what happened   on the unsuccessful PC is it anything to do with 365.
When I look at the programs installed on each PC I can only see reference to 365 although when I do a search I can find Access 2013.

chestera
chesteraAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Could you post the entire message? Might help to track down the trouble.

If the target machines are all using Office 2013, then I'm curious why you are deploying a .mde file. While I understand there is some work involved in upgrading to the .accdb format, you'll find your path much easier if you maintain the same format as the target machine. In my experience, unless you move up to the .accdb format, you'll invariably run into this trouble from time to time.

As with all things like this, be sure the target machines are fully updated. In cases like this, where you're install with an Installer, you might show a dialog that instructs the user to be sure their Windows and Office installations are fully updated prior to running your install.
0
chesteraAuthor Commented:
Scott McDaniel

I made an mde because the app was originally developed in access 2003 is it hard to convert to .accdb. All PC's were running Win 7 with access 2003 now they have updated to win 8 and 365.

Alan
0
chesteraAuthor Commented:
Scott McDaniel

Hi Scott
Sorry for the delay I have been away. I have taken my Program developed in 2003 and imported into access 2013 and compiled into .accdb. It's working at the moment what problems could I face in the future leaving as is or do I need to do more modifications to my code

Alan
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

chesteraAuthor Commented:
Scott Mcdaniel

Here is the error message i get on one of the PC's
This data is unreconized format
The Database may have been created with a later version of Microsoft Access then the one your are using. Upgrade your version of Microsoft Access to the current one, Than this Database

I have office 2013 where the other PC's have 365. To get it working on the PC with the error message I openup office 2013 and recompile .accde then it works. The department have since installed onto more PC's and have to recompile .accde to get it working

I believe 365 and 2013 are one and the same

My PC has Win8 office2013 with SP 1. The other PC's have Win8 and Office SP1

System is 64 bit and Office is 32 Bit

Alan
0
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
If the program seems to be working after conversion, then generally you won't have troubles with it. There were some known trouble areas - for example, some Openform and Openreport code broke - but if you haven't seen troubles, then most likely you won't see troubles.

As to your other issue - 365 is, essentially, Office 2013, but of course 365 can be run "in the cloud" or downloaded onto a desktop. With Access, I'm pretty sure you must download that (unless you're creating a Web App, which you're not), so it's fairly safe to assume that both you and the end users have the same version.

Can you open Access on one of the trouble machines and see exactly which version they're using? To do that, go to the File menu and click Account, then click the About Access button. You should see the full version in that text, towards the top of the information.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
chesteraAuthor Commented:
Scott McDaniel

Info requested

My machine Info
Microsoft Access 2013(15.0.4569.1503) MSO (15.0.4569.1506) 32 bit
Part of Microsoft Office Professional Plus 2013

Product ID: 00216-53040-01457-AA643

Machine giving wrong format
Microsoft Access 2013 (15.0.4505.1000) MSO (15.0.4505.1005) 32 bit
Part of Microsoft Office 365 ProPlus

Product ID: 00202-50086-21955-AA838

Alan
0
chesteraAuthor Commented:
Scott McDaniel

Thank you Scott. I have other questions on this subject so will post another question

Alan
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.