2010 publishing conversion issues

[misscrf]

I have 2010 Access, and was told by client they had most recent. It turns out they have 2007. I had tried to give them an accde, because I want to lock it down. They cannot open that unless they install the 2010 runtime. When they do that, none of their 2007 db's open.

I was trying to convert the accdb that I am developing in, to mdb and then mde, but I get a collating sequence error.

I have researched, but not found a solution. It would seem this would be an issue for others out there.

Anyone have any thoughts?


Thanks!

misscrf

It is never too late to become what you could have been ~ George Eliot

 

[misscrf]

Since I haven't gotten any responses, I thought I would elaborate.

I am developing in 2010. The client told me they had the most recent version, but of course they don't. They have 2007. I had given them an accde because I want to lock down what I have made. They tried to install runtime and say that they can open my app, but none of theirs with the runtime installed. Without it, they cannot run my app.

I have been figuring I could make my accdb (dev version) into an mdb and then an mde for them. For a while I was getting an error about selected collating sequence not supported. It gave me that error trying to make the mdb. It still made it though. Then when I would open the mdb and try to make the mde I would get same error, but it would not make mde.

I have compacted and repaired the accdb. I have compiled the code. Now I can't make the mdb anymore. Now I get an error that says

"The specified database sort order, General, is not supported for the target database format."

I tried General - Legacy (Options - General - New Database Sort Order) The others are different languages.

Nothing seems to be working. Anyone have any ideas?

Thank you,





misscrf

It is never too late to become what you could have been ~ George Eliot

 

[fcortezl]

I had also created a Access:2010 accdb which of course does not open in Access:2007 and which of course you can not easy save a Access:2007 accdb, it defaults to Access:2010 accdb.
So I also created a Access:2003.mdb, which you can save UP in Access:2007 as 2007.accdb and start development again for those Access:2007 user you may have and hope you did not lose to many features or programming.

 

[misscrf]

Thank you for responding. I am not sure I understand your suggestion.

I have an accdb created in 2010. I want to give the client an accde, but they have 2007 and it won't open for them. My other thought is to save the accdb as an mdb and then save the mdb as and mde. This way I still have a compiled and locked down publishable version of the application.

My issue is that I am receiving errors when I try to save to an mdb, and I cannot successfully save a reverted mdb to an mde.

If you have suggestions of how I can resolve these errors or go about this another way, I am definitely interest.

My end goal is to either

1) get their environment to be able to run an accde from me, while still being able to open and use their 2007 apps

or

2) give them an mde which should be ok in their current environment.

I cannot give them an accdb or an mdb because they can edit those and I am intending to publish this solution, not share a development copy.

Thank you.

misscrf

It is never too late to become what you could have been ~ George Eliot

 

[misscrf]

As an update:

We converted all the users current 2000 databases to accdb 2007 format. They all work fine. Then we installed the Access 2010 runtime so that we can run my published accde for their use. Once that is installed we get a series of errors and messages.

When we launch the 2010 accde, the runtime installer starts installing (even though it is already installed) then the user gets a security warning, even though they are on low security in the macro settings. Once you answer yes to open from the security warning, the application runs fine.

Once we close the 2010 accde, we try to open a 2007 accdb. We then get an error "There was a problem sending the command to the program" After that the Office 2007 Hybrid install starts running. Then the 2007 db opens.

If it is helpful to note, they are running Windows 7 and their install of Office Professional 2007 is actually Office Ready which means it came with the computer (OEM).

Last night I actually uninstalled all of Office and the runtime. I reinstalled office, and SP1 and SP2, then the runtime for Access 2010. We still get these installers running when we switch back and forth between the 2007 accdb files and the accde 2010 file.

Can anyone help with ideas of how to stop these installers running every time we launch these files???

Driving me nuts lol.

Thanks!

misscrf

It is never too late to become what you could have been ~ George Eliot

 

[boblarson]

Switching between versions will ALWAYS result in the install stuff happening. This is because certain registry settings have to occur before the version you are wanting to open can be opened. This has been an issue beginning with having 2003 and 2007 installed. There is nothing you can do to stop that.

The reason you cannot convert your 2010 database to a previous version is that you are using features that ONLY exist in 2010 and that can't be stripped out by the conversion process because they are integral to your current database.

As for the security warnings, you need to add the database to a trusted location and to set that location, since you are using the runtime for 2010 you would need to use a batch file or manually go update the registry. See here for more info about that:

http://accessjunkie.com/faq_33.aspx

That link is for 2007 databases but you should be able to use the same registry settings but with ONE CHANGE - change the part that says 12.0 to 14.0

Bob Larson
Free Access Tutorials and Samples:

http://www.btabdevelopment.com

 

[misscrf]

Thanks for the info. I don't see why I can't convert the 2010 db though. It is a really basic app that doesn't have anything new to it. Tables, forms and they are the same as I would have created them in xp, 2003 or 2007.

There should be a way for Access to let you know what components prevent a db from being converted back to 2007 and what needs to be done to make them compatible.

boo lol.

misscrf

It is never too late to become what you could have been ~ George Eliot

 

[boblarson]

There should be a way for Access to let you know what components prevent a db from being converted back to 2007 and what needs to be done to make them compatible."
We suggested that to them in the development phase but they didn't seem to include that. They have a check where you can check to see if it is WEB compatible but not backwards compatible.

Sorry, but if you used any of the new form navigations, etc. it can cause a problem.

Bob Larson
Free Access Tutorials and Samples:

http://www.btabdevelopment.com