Lower your macro security setting:
Tools | Macro | Security | Low
If you do not see that menu option, right-click the toolbar area, customize,
and reset the Menu Bar. For more information, see:
http://office.microsoft.com/assistan...roduct=acc2003
If you are converting applications from A97 to later versions, you may
appreciate:
Converting from Access 97
at:
http://allenbrowne.com/ser-48.html
The article covers:
- setup issues (like the Sandbox mode above).
- conversions issues (problems gettting a file to convert).
- usability issues (problems with the new versions that A97 did not have).
- useful features (new stuff).
- file formats (which to choose).
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"tom r." <ri******@neo.rr.com> wrote in message
news:28**************************@posting.google.c om...
I have a mature application that was developed in A97, converted to
A2K, and everything has been working wonderful. One our plants has
upgraded to Office 2003, so I have just tried to run the A2K version
under A2K3. Most stuff works okay, but a major problem is the use of
expressions for the ControlSource of a textbox. The following
expression works for A97 and A2K, but leaves the textbox blank if run
under A2K3:
=fSetHelpText() 'function will retrieve data and put into the textbox
My references for A2K are the same as A2K3 (except 9.0 Object library
for A2K and 11.0 Object library for A2K3).
Can anyone help me out?
TIA
Tom R