Access 2003 creating OWC 10 objects

[Paul - Lydian]

I want to create data access pages that can be used by clients that have
only the OWC 11 runtime loaded.

When I create a data access page using Access 2003 the objects and classes
inserted are from OWC 10 and not OWC 11. (ie the MSODSC object has a class of
0002E553 instead of 0002E55B). I have OWC 9, OWC 10 and OWC 11 loaded. If I
unregister OWC 10 and create a new data acess page then Access complains that
the data page is corrupt as it is still using the OWC 10 class ids even
though OWC 10 is no longer registered.

How do I reconfigure Access 2003 to create OWC 11 objects and not OWC 10
objects?

Thanks.

 

[Paul - Lydian]

I haven't found a solution to this so I've developed a work around.

As far as I know Office 2003 Professional loads OWC 10 and 11 but Office
2003 Standard only loads OWC 11.

A data access page developed using Access 2003 creates a OWC 10 page and so
can't be used by a client running Office 2003 Standard unless OWC 10 is also
loaded. A bigger problem is that server filters containing brackets under OWC
10 do not work, apparently a known issue.

So to enable development using Access 2003 and deployment with OWC 11 I have
written some software that replaces OWC 9/10 class ids etc. with the OWC 11
equivalents. I have a client with only OWC 11 loaded to prove functionality
etc. is the same as on the development system that has OWC 9, 10 and 11
loaded.

 

[bob]

I have the same prob.... what exactly do you have to do? what bits o
the code do i need to alter/replace? i'm new to all this and it
twisting my melon, man