G
Guest
This is a difficult one to explain, but I am seeing a bug when Access 200
is used on a system with Windows XP (Home or Pro). The problem is with
subform on a wizard
The following code is executed when the user goes to the next page in th
wizard
Select Case mintCurrentPag
Case 1 To 3, 7 To clsAddEntityWiz1.LastPag
Me.fsubPage.LinkChildFields = "MemberID
Me.fsubPage.LinkMasterFields = "txtMemberID
Case 4 To
If IsNothing(Me.txtMemberID_Partner) The
Me.fsubPage.LinkChildFields = "
Me.fsubPage.LinkMasterFields = "
Els
Me.fsubPage.LinkChildFields = "MemberID
Me.fsubPage.LinkMasterFields = "txtMemberID_Partner
End I
End Selec
txtMemberID_Partner is null when the problem occurs. Nevertheless, in ste
4, the page is being displayed as if LinkChildFileds = "MemberID" an
LinkMasterFields = "txtMemberID". This is causing me and my customers a lot of grief wit
users running Access 2002 on Windows XP
The database is compiled in 2000 format. The problem does not occur o
systems with Access 2002 and Windows 2000. Nor does it occur on system
with Access 2000 on any OS. The same code base is used in Access 97...an
the problem does not occur with any OS. Anyone else run into a simila
problem? Any resolution
TI
-
Paul Overwa
Logico Solutions, LL
www.logico-solutions.co
is used on a system with Windows XP (Home or Pro). The problem is with
subform on a wizard
The following code is executed when the user goes to the next page in th
wizard
Select Case mintCurrentPag
Case 1 To 3, 7 To clsAddEntityWiz1.LastPag
Me.fsubPage.LinkChildFields = "MemberID
Me.fsubPage.LinkMasterFields = "txtMemberID
Case 4 To
If IsNothing(Me.txtMemberID_Partner) The
Me.fsubPage.LinkChildFields = "
Me.fsubPage.LinkMasterFields = "
Els
Me.fsubPage.LinkChildFields = "MemberID
Me.fsubPage.LinkMasterFields = "txtMemberID_Partner
End I
End Selec
txtMemberID_Partner is null when the problem occurs. Nevertheless, in ste
4, the page is being displayed as if LinkChildFileds = "MemberID" an
LinkMasterFields = "txtMemberID". This is causing me and my customers a lot of grief wit
users running Access 2002 on Windows XP
The database is compiled in 2000 format. The problem does not occur o
systems with Access 2002 and Windows 2000. Nor does it occur on system
with Access 2000 on any OS. The same code base is used in Access 97...an
the problem does not occur with any OS. Anyone else run into a simila
problem? Any resolution
TI
-
Paul Overwa
Logico Solutions, LL
www.logico-solutions.co