[dba-SQLServer]SQL Server strangeness

John W. Colby jcolby at colbyconsulting.com
Wed Nov 19 06:47:48 CST 2003


Thanks, I'll check that.  I know that SQL Server loads it's own when it
installs.

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of
Francisco H Tapia
Sent: Wednesday, November 19, 2003 1:36 AM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer]SQL Server strangeness


I'd start w/ the MDAC that is loaded on your crashed box, what did you
have before, and what do you have now? get the component checker from
microsoft.com/downloads

I highly recommend MDAC 2.6 sp1 and above.

--
-Francisco

John W. Colby wrote:

> Awhile back I moved my client billing to SQL Server, just a simple upload
of
> the mdb data, and then relinked to the ODBC.  Nothing fancy.
>
> It all just worked.
>
> Now (since recovering EVERYTHING due to a hard disk crash), the LIKE
keyword
> is causing failures in the odbc call.  I use things like "LIKE
> forms!someform!somecontrol" etc.  Now this fails (silently), just no data
> returned.  Replace the LIKE with IN() and it works again.
>
> The TRULY strange part is that I use a LIKE ccfrmWhich() EVERYWHERE in
order
> to only display active records in my forms.  That fails in a combo, but
> succeeds in the form that hosts that combo.
>
> I do so love Access / SQL Server.
>
>
>
> John W. Colby
> www.ColbyConsulting.com
>
>



_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com






More information about the dba-SQLServer mailing list