RE: ODBC -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: ODBC
From: "Dave Snyder" <dsnyder@xxxxxxxxxx>
Date: Tue, 25 Oct 2005 15:35:57 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Message we get is SQL0901 - SQL system error.


>>> thatzenbeler@xxxxxxxxxxxxx 10/25/05 3:28:06 PM >>>
Are they getting an error message?  If so what is it?

I had a problem a few years ago, with crystal reports, because the
reports
stores the database name, and when we got a new server, the database
name
changed, so I had to re-update all those reports...  The odbc DSN name
still
stayed the same...  It was an as/400 setting that changed...  

Tim

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.