in reply to Re: win32::odbc/ SQL error
in thread win32::odbc/ SQL error

Yes, of course I should have put error handling in. D'oh! However, after doing so, I'm not getting any connect errors. I'll go and check those field names again...

Replies are listed 'Best First'.
Re: Re: Re: win32::odbc/ SQL error
by JamesNC (Chaplain) on May 23, 2003 at 01:56 UTC
    ... <Data> probably should just be data or data when you have table or column names that have spaces in them you use square brackets ex: SELECT data.first name, data.last name, machine.user name FROM data, user WHERE ... blah, blah...the error you are seeing is because the DB is telling it.. <DATA> is not a name of a table unless you named your table '<DATA>'?
    I do have one suggestion... try DBI, just my 2cents... JamesNC
Re: Re: Re: win32::odbc/ SQL error
by hangmanto (Monk) on May 23, 2003 at 04:14 UTC
    After inserting the error checking, are you geting the same error message? Your previous error message indicated that the $db variable was not defined. That indicates that your 'new' statement is failing. Fix that before moving on.

    I agree with JamesNC. I would use DBI. The knowledge you gain from using it on MS SQL would be (mostly) transferable to Oracle, mysql, etc. Just my 2 cents.

    Most importantly, don't give up. Keep plugging away. It's worth it.