M
mdupris
I'm trying to make a splitform within an Access 2007 ADP file which
uses a SQL Server table as its record source. However, as soon as I
add a "Form_Load()' or 'Form_Current()' macro -- even one with no code
within either macro -- and click into Form view, I get a pop-up "The
expression On Current you entered as the event property setting
produced the following error: A problem occurred while Microsoft
Access was communicating with the OLE server of ActiveX control".
Commenting out those lines solve the problem. Other macros, e.g.
*_Click() events, run just fine.
Since there are changes to be made on the non-datasheet part of the
form depending on the current row in the datasheet section, the
Form_Current() would be intensely useful. I've not seen reports of
this specific bug. Anyone have any clues or, even better,
alternatives?
= M =
uses a SQL Server table as its record source. However, as soon as I
add a "Form_Load()' or 'Form_Current()' macro -- even one with no code
within either macro -- and click into Form view, I get a pop-up "The
expression On Current you entered as the event property setting
produced the following error: A problem occurred while Microsoft
Access was communicating with the OLE server of ActiveX control".
Commenting out those lines solve the problem. Other macros, e.g.
*_Click() events, run just fine.
Since there are changes to be made on the non-datasheet part of the
form depending on the current row in the datasheet section, the
Form_Current() would be intensely useful. I've not seen reports of
this specific bug. Anyone have any clues or, even better,
alternatives?
= M =