T
Tony in Michigan
Hello!
One of the very generous group contributors provided the SQL below for a
project I am working on.
I have a slight dilema.
Table 1 has many fields with many data types. If I run it as is, I get a
data mismatch in criteria error . To get around this, I have made an
alternate table 1, which only has the field I am comparing to table 2. It
now works perfectly.
My issue; This is run accross a network via a Citrix process, so there is a
system time limit.
The process to create the alternate table 1 eats up a lot of the connection
time. Now I've mitigated this somewhat, by limiting the time frame to
include on the table.
The question:
Is there a way to trick the system into dealing with the multiple data
types? Is this something as simple as too many fields?
SELECT Table1.*, Table2.*
FROM Table1 INNER JOIN Table2
ON Replace(Left(Table1.FieldName, 13), "-", "") = Table2.FieldName
One of the very generous group contributors provided the SQL below for a
project I am working on.
I have a slight dilema.
Table 1 has many fields with many data types. If I run it as is, I get a
data mismatch in criteria error . To get around this, I have made an
alternate table 1, which only has the field I am comparing to table 2. It
now works perfectly.
My issue; This is run accross a network via a Citrix process, so there is a
system time limit.
The process to create the alternate table 1 eats up a lot of the connection
time. Now I've mitigated this somewhat, by limiting the time frame to
include on the table.
The question:
Is there a way to trick the system into dealing with the multiple data
types? Is this something as simple as too many fields?
SELECT Table1.*, Table2.*
FROM Table1 INNER JOIN Table2
ON Replace(Left(Table1.FieldName, 13), "-", "") = Table2.FieldName