Linking Table Manager apparent difficulty effecting query speed dramatically

[SemiAuto40]

I have a split database and started having problems after a new better faster server was installed. But I can't totally blame the server because when I relocate the main table 'tbl_Sample_Login' on to another network location/drive my personal drive H: then I get the same problem!!!

I rebuilt the query one field parameter at a time and ran itagainst the back end. All resultsreturned quickly UNTIL I added the most important parameter and that was thedate range to get the last 7 days of the rest of the stuff.
However when I use a WHERE statement on my short date format...
"WHERE(((tbl_Sample_Login_table.LoginDate)=Dat e()-7))"
(where I want to get the subset of records that are from thepast 7 days only). BTW, the fieldLoginDate is a short date format.
It seems to me as though the query itself in Access frontend is put together, converted to sql, or something at the front end Accessprogram. Is there some setting perhapsthat I could have jacked up with Access?

[RuralGuy]

Could there be some TIME component messing things up? http://support.microsoft.com/kb/q130514/en-us

[SemiAuto40]

My query is in my original post. The field in the table is a "short date". It has been working for a couple of years.. so something happened with Access or my network when they replaced the server with a better one. I have relinked the tables. I have located the main table on a network drive H: in my case and have the same dreadful performance. Other network functions and queries operate OK. This is a big deal for me.
Thanks.

[RuralGuy]

I would think the WHERE clause would be something like: "WHERE(((tbl_Sample_Login_table.LoginDate)>=Da te()-7))"
It does not explain your speed issue but I was curious.