------_=_NextPart_000_01C3479E.D981C070
Content-Type: text/plain

I am having problems using Crystal Reports to report on the RT (Request
Tracker) database which is a MySQL Database.

I am using Crystal Reports 8.0.1.0
RT Version 1.0.6
MySQL ODBC Driver 3.51
MySQL 3.23.54

We have some reports which have been running for some time on a machine
using a User DSN under Windows 2000.
I now want to run them on my machine (Windows XP) but I get an error
<<error mess.jpg>>
I have tried using both User and File DSNs but always get the same result. I
have tried on Windows 2000 laptop similar to the one it used to be run on
with the same result. I have also tried it on a Windows NT machine. Always I
get the same result.

Another colleagues working on the same NT machine with an identical User DSN
can get it to run. He can even run it using a file DSN.
He has tried on my machine but it gives the same error message.

I have looked at the SQL Code after it fails for me and when it works and it
is different. The good code is
<<sql.txt>>
The bad code is
<<badsql.txt>>
I also enclose a copy of the report in case that helps.
<<Time to fix date selection.rpt>>

Henry Jones
IS Manager
Dynex Semiconductor Ltd
01522 502729



------_=_NextPart_000_01C3479E.D981C070
Content-Type: text/plain;
name="sql.txt"
Content-Disposition: attachment;
filename="sql.txt"

SELECT
each_req1.`serial_num`, each_req1.`status`, each_req1.`date_created`, each_req1.`date_acted`,
transactions1.`serial_num`, transactions1.`trans_date`
FROM
`each_req` each_req1,
`transactions` transactions1
WHERE
each_req1.`effective_sn` = transactions1.`effective_sn` AND
each_req1.`serial_num` = transactions1.`serial_num` AND
each_req1.`status` = 'resolved'
ORDER BY
transactions1.`serial_num` ASC,
each_req1.`serial_num` ASC
------_=_NextPart_000_01C3479E.D981C070
Content-Type: text/plain;
name="badsql.txt"
Content-Disposition: attachment;
filename="badsql.txt"

SELECT
each_req1.`serial_num`, each_req1.`status`, each_req1.`date_created`, each_req1.`date_acted`,
transactions1.`serial_num`, transactions1.`trans_date`
FROM
{ oj `each_req` each_req1 INNER JOIN `transactions` transactions1 ON
each_req1.`effective_sn` = transactions1.`effective_sn` AND
each_req1.`serial_num` = transactions1.`serial_num`}
WHERE
each_req1.`status` = 'resolved'
ORDER BY
transactions1.`serial_num` ASC,
each_req1.`serial_num` ASC

------_=_NextPart_000_01C3479E.D981C070
Content-Type: text/plain; charset=us-ascii

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org
------_=_NextPart_000_01C3479E.D981C070--

That pretty much says it all. I'm waiting for 4.0.14



--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org

On Fri, 2003-07-11 at 04:23, Henry Jones wrote:

Hi !!

> I am having problems using Crystal Reports to report on the RT (Request
> Tracker) database which is a MySQL Database.
>
> I am using Crystal Reports 8.0.1.0
> RT Version 1.0.6
> MySQL ODBC Driver 3.51
> MySQL 3.23.54
>

Looks like the error image is filtered by the list, so couldn't help
you.

The best way is to file a bug report in bugs.mysql.com with related
attachments, so that we can comment further.

Also provide the following information:

MDAC version on working and non-working systems.

Thanks

> We have some reports which have been running for some time on a machine
> using a User DSN under Windows 2000.
> I now want to run them on my machine (Windows XP) but I get an error
> <<error mess.jpg>>
> I have tried using both User and File DSNs but always get the same result. I
> have tried on Windows 2000 laptop similar to the one it used to be run on
> with the same result. I have also tried it on a Windows NT machine. Always I
> get the same result.
>
> Another colleagues working on the same NT machine with an identical User DSN
> can get it to run. He can even run it using a file DSN.
> He has tried on my machine but it gives the same error message.
>
> I have looked at the SQL Code after it fails for me and when it works and it
> is different. The good code is
> <<sql.txt>>
> The bad code is
> <<badsql.txt>>
> I also enclose a copy of the report in case that helps.
> <<Time to fix date selection.rpt>>
>
> Henry Jones
> IS Manager
> Dynex Semiconductor Ltd
> 01522 502729
>
>
>
> ____________________________________________________________ __________
> --
> MySQL Bugs Mailing List
> For list archives: http://lists.mysql.com/bugs
> To unsubscribe: http://lists.mysql.com/bugs?unsub=venu [at] mysql.com
--
Venu, Software Developer
Palo Alto, CA, USA
MySQL Inc, http://www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org

Hi!

On Jul 11, Adam Pedersen wrote:
> That pretty much says it all. I'm waiting for 4.0.14

No.

and -

It's being built right now.
Probles with some platforms (like AIX and HPUX) may delay release a bit,
but it should be out next week. Unless there will be a critical bug
found, of course.

Regards,
Sergei

--
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <serg [at] mysql.com>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer
/_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
<___/ www.mysql.com

--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs [at] m.gmane.org