Conversion Issues 2003 to 2010

[PiedPiper70]

I have a large application originally written in Access 2003 running on XP. My development machine has been upgraded to Windows 7 but still keeping Office 2003 Pro. At the same time our client has also been upgraded to W7 with Office 2010 standard and Access 2010 runtime. This is all working fine.

Now it's time to upgrade my development machine Access 2010 proper. But this is where I'm getting problems - the program won't compile on a test machine. I tried creating a blank 2010 version and importing all the objects, but I get a mass of compile errors.

For example, the compiler doesn't like "Dim wordObj as Word.Application" which I use a lot when creating word documents from templates using bookmarks.

What I can't understand is why this app runs quite happily under Access 2010 Runtime?

Can anyone throw any light on this to help me understand what I need to do to create a successful 'accdb'

Thanks
Dave

 

[DavidAtWork]

that is strange because I thought the run-time uses the equivalent of a .mde file and in order to create that, it has to compile.
What happens if you try to open a copy of the 2003 file from A2010, does it not give you the option to convert to a 2010 accdb version

David

 

[PiedPiper70]

A bit more info:-

In full version of A2010 my app, which is still an .mdb, runs without errors but there are issues mainly around menus/toolbars/ribbons. The locking down that I do in A2003 doesn't work right and menus and ribbons are exposed for all to see.

In A2010 Runtime it works perfectly without me touching anything.

If I open the app in A2010 full version I am able to convert to .accdb but this is where the problems lie. I get a large number of compile errors - so many that I've never completed the job.

So my current view is that I'm going to stick with mdb and do what's necessary to lock it down - which in fact I have managed to do in since my first posting. So I'm happy.

I may be missing features of an .accdb but I can live with that.