in reply to Re^2: DBI SQL error messages
in thread DBI SQL error messages

I wonder if that's just because the way the GUI works

That's right. If you bypass the GUI (what Access calls Design View), you can run an INSERT ... VALUES statement against an Access database, just as DBI does.

Ask the GUI to display what you just did, and it converts the VALUES list to a SELECT clause without a FROM clause. If you don't want to see this happen, stay in SQL view.

Replies are listed 'Best First'.
Re^4: DBI SQL error messages
by rjberry (Novice) on Oct 13, 2008 at 08:52 UTC

    Hiya, I've found out what it is actually. There's nothing wrong with my SQL, it's instead to do with how MSAccess treats its version of Text fields, which is Memo fields. For some reason it's not really compatible with DBI. There's a post about it here, although their fix didn't work for me, sadly.

[reply]

In Section Seekers of Perl Wisdom