Originally Posted by
Ed Jobe
Melanie, don't just call the query and let it prompt you for a parameter. Call a custom input form, then pass that data to the query. You can design the custom form however you like.
The main reason for going to sql would be for multiple user access. But to keep it simple, Access is fine. To prevent file locking issues with Access, I just finished one with a back-end/front-end. The front end links to tables in the back end. That way multiple users can have the gui open (a copy on their pc) and access to the back end is handled at the record locking level. But if you did go to .NET and sql, you could make use of data binding and workflow. On the other hand, Access is easy to generate reports for. It still has its place.