P
peter
I upgraded from Access 2002 to Access 2003. Since
performing the upgrade, the Script Debugger will not
allow me to debug a Data Access Page. When you start to
debug, an IE window opens, but it is blank. It appears
that the controls are not binding to the database. MSFT
replicated the issue, which they believe was introduced
from a specific SP for Access 2002 which also impacts
Access 2003. If you open the Northwind Sample DB and
select a DAP and invoke the Script Editor and try to
debug, you should encounter this issue.
Just thought I would post this to see if anyone has any
ideas about a workaround.
performing the upgrade, the Script Debugger will not
allow me to debug a Data Access Page. When you start to
debug, an IE window opens, but it is blank. It appears
that the controls are not binding to the database. MSFT
replicated the issue, which they believe was introduced
from a specific SP for Access 2002 which also impacts
Access 2003. If you open the Northwind Sample DB and
select a DAP and invoke the Script Editor and try to
debug, you should encounter this issue.
Just thought I would post this to see if anyone has any
ideas about a workaround.