You have a couple options.

One, redevelop the solution using an .adp file instead of an .mdb file. This is not trivial, and you may have to find new solutions...

You don't actually want a trigger, since a trigger is activated by table activity, not time. What you want is probably a scheduled job.

Are you using Access as the data store, or just a front end? Are you trying to do this with a pass-through query?

Why aren't you just doing this with...

Also, you want to use single quotes instead of double quotes.

So, assuming Tran_Code and Amount are numeric data types and the others are not:

('AA' + [Org] + '00' + [Acct_Nbr]...

No problem!

Oh. In that case, use the first suggestion. Create a field on your form for the user to enter the search criteria. Set the recordsource of the...

Essentially correct. For what you want to do, workgroups will be the best way to go.

Correct. Any data changes that take place in the front end affect the back end automatically through the linked tables.

As a note, if the only thing you're trying to...

This is absolutely possible. The actual mechanics for doing it depend on your set-up.

If you're using a .mdb file with linked tables, create a query with the various search...

Oh, right. In my head, I'd already pulled out the apostrophe, because it looked like he was trying to use integer values. So, there should have been an...

Just put a copy of the .mdb file on their PC. The links to the SQL Server should still work. So, all the data should be flowing exactly...

Er, just out of curiosity, does your original SQL have the curly bracket } at the end? Because, it should have square brackets on both sides.

Well, more like:

pid="2;DELETE FROM table;"

Put that into your SQL, and remember that semicolons terminate SQL statements. Some yahoo has just passed a statement into your system that retrieves your...

Each user will need to connect to the workgroup file.

Caveat #1: If you simply have each user join the workgroup file, then that security will apply to every Access...

In T-SQL, if you surround a value with double-quotes, it interprets it as a column name. Or, in your case, it interprets it as a column name when you...