Hey folks,
We've had what I'll call *limited* success using the old SQL 6.5
driver (i.e., sqlsrv32.dll from the 6.5 installation). We can generate
an EOModel of our database using this, but consistently encounter two
problems when trying to use a Wizard-generated test app:
1) Mismatched data types errors -- we have yet to determine which column
is the problem with this one.
2) Locking problems. When we have two rows in the table, and try to
update just one of them (and they do have unique PKs), EOF fails
with a message like "Lock returned for two rows -- aborting", or
words to that effect. Maybe someone should tell EOF that MS-SQL
doesn't support row-level locking? The SQL generated tries to
select with the HOLDLOCK keyword -- essentially a select for update.
But SQL Server locks the whole page, not just the one record.
Aaaaarrrrggghhh.
This is really getting to be frustrating. Some of the developers on
the project are ready to give up and just use ASP (OK, they're Micro$oft
bigots anyway).
Any ideas greatly appreciated. Nader from Apple had suggested earlier
trying to get a stack trace from EOF when it crashed...but its no longer
crashing, just failing. Any ideas? Anyone?
On Feb 21, 4:07pm, Paul Naro wrote:
> Subject: Re: ODBC and MS-SQL 7, WO 3.5.1
> > Fellow WOers,
> > I'm (still) using WOF 3.5.1, and am trying to connect to
> > MS SQL Server 7.0 with ODBC 3.51 - EOModeler is DR. Watson-ing with
> > some ugly error. Has anyone successfully used this stuff with
> > MS-SQL 7.0 drivers? Is there a trick to it? I'm using the
> > ODBC Adaptor Patch #2602 from NextAnswers. A similar config on
> > another box works great with MS-SQL 6.5 - but with an older ODBC
> > version.
>
> Ditto with WO4. Does anyone have WO or EOModeler working with SQL Server 7
> via ODBC?
>
>
> Regards,
>
> Paul J. Naro
> Timberline Webworks
> http://www.tlww.com/
>-- End of excerpt from Paul Naro
--
Troy D. Casey -- [EMAIL PROTECTED]
"A civilized society is one which tolerates eccentricity to the point of
doubtful sanity."
-- Robert Frost
