Data Access Page created with Access 2000

D

doris_g

I created several DAP pages with Access 2000 that are used extensively by
many users with no problem. My users who have moved to Office 2003 cannot
view any data on these pages--all they see are page headers. HELP!
 
T

Todd Pendleton

MS is vague about interversion compatibility of DAPs.

Have you tried opening the DAPs in 2003 for editing, and then saving. That
might convert them so that they conform to 2003 standards. It would be a
good experiment, and we would be interested in your results, also wanting to
know whether a later Officer version will "update" an DAP created in an
earlier version of Access.
 
D

doris_g

When I brought my DAP pages up in Access 2003, it told me they were built
with an earlier version of Offce Web Components, disabled the pages, and
wouldn't let me go into Design mode. I went into the HTML and stripped out
the OWC-generated code and was then able to go into Design mode, but I found
none of the drop-downs worked anymore--they only provided one response in the
drop-down (ex. Yes/No, only Yes appeared). So I ended up recreating all of
my pages--not fun! I work for a large company and we are slowly migrating to
Office 2003. Now I'm trying to figure out how I can create one set of pages
that will work for people still on Office 2000, as well as those who are now
on Office 2003--our migration will run over about 8 months and the OWCs for
2000 are not compatible with the 2003 OWCs & there doesn't appear to be an
easy way to update to 2003 if you're still on Office 2000. I'm further
along, but still nowhere. Thanks for your response.
 
E

erikdenkers

I was having the same problem. What I did was made sure that my computer
(the "development" pc), had the Office Web Components installed from the
Access 2000 installation - nothing else from that version.

Once I had both versions of the Office Web Components (from Office 2000 and
Office 2003), I was then able to open my older data access pages and was
prompted to upgrade them.

Please note, some of the custom scripting that you may have added to your
Data Access Pages with Office 2000 may no longer work with Office 2003.

Users will need to download and install the OWC version 10
 
P

PPGDDT

I've seen this problem as well. The dilemma that we face is that the Access
2003 DAP tries to automatically update to the OWC v10 (Office XP) components
and NOT the OWC v11 (Office 2003) components. Our users have installed
Office 2003 and have ONLY the Office 2003 version (v11) of the components.
So, they get errors when running our pages that contain v10.

Why would Microsoft update the OWC to v10 when in Access 2003??
Is there anyway that I can set some default on my developers' workstations
to upgrade the DAP to OWC v11 instead of OWC v10??

Any advice is greatly appreciated!
 
Top