> Does anyone have a good pointer on what's required to compile DBI > under Windows (using the ActiveState base)?
The general rule is you need the same compiler that was used to compile the Perl you're using. For ActiveState, that's Microsoft Visual C++. Other than that, there's not much in the way of prerequisites. This mail reminded me to upgrade to 1.48 on this machine, and all I needed to do was open a Visual Studio .NET command prompt (i.e. just the shortcut to a normal command prompt but it runs vcvars32.bat) and run "cpan DBI" which fetches, compiles and installs it. > And, while I submitted a bug fix req quite a while ago and had it > fixed for *nix (the ability to use question marks in field names > primarily by hacking the back-tick operator as a quoting character) I > was wondering if anyone came across said problem under Windows and > managed to solve it... Can't say I've ever thought about having question marks in field names other than with a sense of horror ;-) but shouldn't that be down to the DBD and database's native quoted-identifier syntax (i.e. double quotes as standard, or backticks on MySQL, and doesn't Access use square brackets?) rather than up in the DBI level? -- Andy Hassall <[EMAIL PROTECTED]> / Space: disk usage analysis tool <http://www.andyh.co.uk> / <http://www.andyhsoftware.co.uk/space>
