SQL vs. Access

[Guest]

We just moved the Access database back-end to SQL. All queries are in the
Access front-end. Should I move the queries used for Mail Merge to SQL, or
keep them in the Access front end?

 

[Guest]

Yes, because you moved the backend to SQL so you placed the tables on the
server. All the other objects are still in your Front_end.

hth

 

[Baz]

Huh? He can't just move the queries to "SQL" (presumably he means "SQL
Server"). What does that even mean? If it means replacing Access queries
with linked SQL Server views, I guess he could do that (at a considerable
cost in time if there's a lot of them), but chances are he'd then finish up
having to rewrite half the application.

No, leave the queries as they are. Only rewrite them as SQL Server views,
pass-through queries or whatever in the instances where performance problems
become apparent.

 

[Guest]

Just to confirm - I should run the mail merge queries from SQL because that
is where the tables are located. Even though all current queries are located
in the Access front-end.

 

[Baz]

Just to confirm, that's garbage. And it's "SQL Server", not "SQL".

 

[John W. Vinson]

Just to confirm - I should run the mail merge queries from SQL because that
is where the tables are located. Even though all current queries are located
in the Access front-end.

No, you should NOT.

The mail merge is based on the Queries, not directly on the tables.

John W. Vinson [MVP]