<= changes to <?

B

Bill McCarthy

I have an Access application in which I invoke a report or a form with a
where clause. In all cases the where clause is of the form:

ServiceDate >= #01/01/2007# And ServiceDate <= #09/25/2007#

This runs just fine. I transmitted the MDB file to a client using FTP.
when he received it, the <= in all cases had changed to <? in the compiled
code ONLY. The source was still correct. I had to go into each code module
and force a source change so it would recompile.

Any ideas on how or why this happened?
 
S

SteveM

I wonder if you may have more luck with Between?

ServiceDate Between #01/01/2007# And #09/25/2007#

Steve
 
6

'69 Camaro

Hi, Bill.
Any ideas on how or why this happened?
Click to expand...

Perhaps you have Track name Autocorrect Info turned on? It could be fixing
your queries for you when the database is opened and different file paths
exist on the new user's computer and Track name Autocorrect gets a bit
carried away with its automatic corrections. It's best to keep this feature
turned off.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
D

Dirk Goldgar

In
Bill McCarthy said:
I have an Access application in which I invoke a report or a form
with a where clause. In all cases the where clause is of the form:

ServiceDate >= #01/01/2007# And ServiceDate <= #09/25/2007#

This runs just fine. I transmitted the MDB file to a client using
FTP. when he received it, the <= in all cases had changed to <? in
the compiled code ONLY. The source was still correct. I had to go
into each code module and force a source change so it would recompile.

Any ideas on how or why this happened?
Click to expand...

Did you FTP in text mode rather than binary mode, by any chance?
 
Top