AS/Perl 5.8.4.810 problems with Tk::DBI::Table on Win-XP

jdtoronto has asked for the wisdom of the Perl Monks concerning the following question:

I got a call from a user just now, and whilst I can replicate his problem, I am not sure how to go about solving it!

The application was written about 12 months ago, using AS/Perl on XP, but probably about 5.8.0 or 5.8.1 or so. The Application launches, but when we go to create a window using Tk::DBI::Table the system just hangs! The module is present, but I have yet to write some test code to see what is going on.

However I am a little perplexed because using -W on the command line produces no output in relation to this at all! The query runs correctly on the mysql command line.

Any clues anyone?

jdtoronto

update title to include reference to Tk::DBI::Table - thanks jdporter

Comment on AS/Perl 5.8.4.810 problems with Tk::DBI::Table on Win-XP

Replies are listed 'Best First'.
Re: AS/Perl 5.8.4.810 problems with Tk::DBI::Table on Win-XP by talexb (Chancellor) on Aug 30, 2004 at 19:02 UTC
Are you using -w or -W on the command line? The former is the one that gives you info on what's going on. Not sure what the latter does. Problems with DBI suggest adding the good old `$dbh->trace(2,'path/to/log.file')` in your code somewhere. At least if you can confirm that the SQL is not a problem you can look elsewhere for the problem. And don't forget to go back to `$dbh->trace(0)` when you're done. Alex / talexb / Toronto "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds	[reply] [d/l] [select]
Re^2: AS/Perl 5.8.4.810 problems with Tk::DBI::Table on Win-XP by jdtoronto (Prior) on Aug 30, 2004 at 20:00 UTC
Thanks Alex! When I posted I had just discovered the problem. For some reason my Windows installation is not showing error dialogues when it should. So as part of the process I took a clean linux box and installed Perl and all the modules on there. Turns out that I made a typo in the original version, but it was not detected and everything worked ok! But in the later version of the module it causes and error. I could see the error dialog on the linux machine and solvede the problem. jdtoronto	[reply]