> > I'm going to try that. I think I have MSVC 6.0 with no > Service Packs installed.
You can safely use SP3. > > What are the problems with higher Service Packs? SP4 changed the in-memory object layout. It was discussed on ActiveState's mailing list over a year ago and it's hard (very) to find, even if you know what you are looking for. It took me a while to find it (maybe I'm not as good of a "searcher" as I should be but SP4 is to vague and finding the right wording took me a while and weeding through the results). > > Can it compile under the Visual Studio NET version of VC? Probably not with 5.6, there are reports on ActiveState's mailing lists about using VC7 with 5.8, but you get a different run-time library requirement. From my experience that's almost always a bad thing, especially due to memory allocation issues (one library allocates, the other tries to free...nasty!!!). YMMV. I have VC.net installed for work projects and VC98 installed for Perl. I do have both. My command line uses VC98 settings and I end up using VC.net only in the GUI. > > > Thanks for the info. I'll let you know the status.... Nop problem. Regards, Jeff > > > > > I installed the DBI and DBD::Oracle modules on a server by > > copying all the > > required files from my workstation. I had originally used > > the files that I had > > pulled from ActiveState via ppm. When I encountered issues > > (DBD::Oracle is old > > on ActiveState), I downloaded the latest from CPAN and > > compiled it manually > > with nmake. > > > > I can connect to the database and issue request through > > dbish, but when I try > > to execute fetchrow_hashref in the script, it just quits > > without any error > > message. I found out that I am geting a Signal SEGV on NT > > through the Perl > > debugger. > > > > I couldn't find anything meaningful with DBI tracing on, but > > can supply a trace > > dump if necessary. > > > > Note that I am using Oracle 9.2.0.1 on Windows 2000 Server. > > You didn't mention it, but: > Are you using MSVC 6.0 SP3 to compile? > > If you are using a different compiler or even SP4 (or above), > you will have significant problems. > > You need to backup to SP3 or use pre-compiled modules which > were compiled with the correct compiler. > > Jeff > > >
