What exactly does "doesn't work" mean? Do you get error messages? Does nothing happen? Do you get the wrong results?
Was this search function written in code or with en embedded macro? Code does not run in 2007 unless your database resides in a folder that has been declared a “trusted” location.
To trust your folder, click:
Office Button (top left)
Access Options (bottom of dialog)
Trust Center (left)
Trust Center Settings (button)
Trusted Locations (left)
Add new location (button)
If that doesn't work, consider this: When apps run fine on one machine and not on another or run fine in one version and not when run under a newer version, one thing you have to think about are missing references.
Here are Doug Steele's instructions on how to troubleshoot the problem:
*** Quote ***
Any time functions that previously worked suddenly don't, the first thing to suspect is a references problem.
This can be caused by differences in either the location or file version of certain files between the machine where the application was developed, and where it's being run (or the file missing completely from the target machine). Such differences are common when new software is installed.
On the machine(s) where it's not working, open any code module (or open the Debug Window, using Ctrl-G, provided you haven't selected the "keep debug window on top" option). Select Tools | References from the menu bar. Examine all of the selected references.
If any of the selected references have "MISSING:" in front of them, unselect them, and back out of the dialog. If you really need the reference(s) you just unselected (you can tell by doing a Compile All Modules), go back in and reselect them.
If none have "MISSING:", select an additional reference at random, back out of the dialog, then go back in and unselect the reference you just added. If that doesn't solve the problem, try to unselect as many of the selected references as you can (Access may not let you unselect them all), back out of the dialog, then go back in and reselect the references you just unselected. (NOTE: write down what the references are before you delete them, because they'll be in a different order when you go back in)
For far more than you could ever want to know about this problem, check out
http://www.accessmvp.com/djsteele/Ac...nceErrors.html
Just so you know: the problem will occur even if the library that contains the specific function that's failing doesn't have a problem.
**** End Quote ****
Welcome to Bytes!
Linq ;0)>
9
