I have an app that was originally developed on Access 97, and I've ported it over to Access XP with minimal problems, which I sorted out. Being nice, I thought I'd check if there were any problems using it on Access 2003. There were!
The forms have quite a few text boxes which lookup and perform calculations based on other controls on the form. These all work fine on 97 and XP, but on 2003, they all display #NAME?.
I think it's down to 2003 being more stringent on subform reference syntax, and the use .FORM, because I changed one to include this and it worked fine, but if I try to change more than one it crashes the whole thing!
Does anybody know if there is a particular reason for this, or if there are any known issues relating to Access 2003 forms? Or even a pointer in the right direction as to who I might get around this. This has stumped me.
The forms have quite a few text boxes which lookup and perform calculations based on other controls on the form. These all work fine on 97 and XP, but on 2003, they all display #NAME?.
I think it's down to 2003 being more stringent on subform reference syntax, and the use .FORM, because I changed one to include this and it worked fine, but if I try to change more than one it crashes the whole thing!
Does anybody know if there is a particular reason for this, or if there are any known issues relating to Access 2003 forms? Or even a pointer in the right direction as to who I might get around this. This has stumped me.
