× 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: BPCS 6.0.2 Mixed mode and Client Access (ODBC)
  • From: "Antun Kolar" <kolarantun@xxxxxxxxxxx>
  • Date: Mon, 04 Jan 1999 09:46:43 PST

Well Microsoft don’t have ODBC Driver for DB2/400, they made ODBC 
Manager for different database drivers. My Company use CA 3.1.3 and 
3.1.2 ODBC Driver without problem  
with Access and Crystal Report.


>From uucp@Uucp1.mcs.net Mon Dec 28 18:08:23 1998
>Received: from [192.160.127.90] by hotmail.com (1.0) with SMTP id 
MHotMail30923500802954563506532481323174383414320; Mon Dec 28 18:08:23 
1998
>Received: from uucphost.mcs.net (Uucp1.mcs.net [192.160.127.93]) by 
Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id UAA25256; Mon, 28 Dec 1998 
20:04:32 -0600 (CST)
>Received: (from uucp@localhost)
>       by uucphost.mcs.net (8.8.8/8.8.8) id UAA21959;
>       Mon, 28 Dec 1998 20:04:31 -0600 (CST)
>Received: (from majordom@localhost)
>       by midrange.com (8.9.1/8.9.1) id TAA30358
>       for bpcs-l-outgoing; Mon, 28 Dec 1998 19:46:03 -0600
>Received: (from uucp@localhost)
>       by midrange.com (8.9.1/8.9.1) with UUCP id TAA30248
>       for BPCS-L@midrange.com; Mon, 28 Dec 1998 19:31:32 -0600
>Received: from hotmail.com (f313.hotmail.com [207.82.251.226])
>       by uucphost.mcs.net (8.8.8/8.8.8) with SMTP id TAA20102
>       for <BPCS-L@midrange.com>; Mon, 28 Dec 1998 19:26:25 -0600 (CST)
>Received: (qmail 18108 invoked by uid 0); 29 Dec 1998 01:25:38 -0000
>Message-ID: <19981229012538.18107.qmail@hotmail.com>
>Received: from 12.69.4.61 by www.hotmail.com with HTTP;
>       Mon, 28 Dec 1998 17:25:36 PST
>X-Originating-IP: [12.69.4.61]
>From: "Paul Holstein" <holstein13@hotmail.com>
>To: BPCS-L@midrange.com
>Subject: Re: BPCS 6.0.2 Mixed mode and Client Access (ODBC)
>Date: Mon, 28 Dec 1998 17:25:36 PST
>Mime-Version: 1.0
>Content-Type: text/plain
>Sender: owner-bpcs-l@midrange.com
>Precedence: bulk
>Reply-To: BPCS-L@midrange.com
>X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)
>
>Thanks for your comments Joe,
>
>Can MS Access use the ODBC drivers from Microsoft to access the AS400?  
>I have heard that this is possible but I have never seen it done.  I 
>have always connected with either Netsoft router ODBC driver or Client 
>Access ODBC driver (I prefer client access because of the lack of an 
RDB 
>entry).
>
>If anyone has ever connected to the AS400 using only Microsoft's ODBC 
>drivers, I would love to hear from you.  Also, maybe someone could shed 
>some light on the relationship of these drivers to each other.  My 
>impression is that each one is mutually exclusive and that you don't 
>need both client access and MS ODBC drivers.
>
>--Paul
>>
>>
>>Paul,
>>
>>You may want to try loading client access and the netsoft drivers 
first
>>then load the new version of the ODBC drivers from Microsoft.  I have 
>ran
>>into similiar problems when I load software out of sequence.  There is
>>really no set sequence, but I have found that Client Access does not 
>work
>>well with the ODBC drivers from Microsoft.  IBM, the last time I 
>checked
>>with them, supported version 2.7 ODBC drivers from Microsoft.  I got 
it 
>to
>>work by installing Client Access first and installing the netsoft 
>drivers,
>>then install the lastest version of the ODBC drivers.  We are 
currently 
>on
>>V3R1M3 of client access and version 4.1 of the OS/400.
>>
>>Hopefully the same principals apply in version 3.2M0 of client access.
>>
>>Let me know what you find out.
>>
>>Joe Royer
>>
>>
>>
>>
>>"Paul Holstein" <holstein13@hotmail.com> on 12/25/98 11:43:40 AM
>>
>>Please respond to BPCS-L@midrange.com
>>                                                              
>>                                                              
>>                                                              
>> To:      BPCS-L@midrange.com                                 
>>                                                              
>> cc:      (bcc: Joey L Royer/Atlanta/Packaging/Mead)          
>>                                                              
>>                                                              
>>                                                              
>> Subject: Re: BPCS 6.0.2 Mixed mode and Client Access (ODBC)  
>>                                                              
>>
>>
>>
>>
>>
>>
>>Tom,
>>
>>I've had terrible problems with AS/400 OS V4R2 and the ODBC drivers 
>from
>>both Client Access and Netsoft.
>>
>>I called Netsoft and they said they never tested the drivers with 
V4R2.
>>My problem is only with certain BPCS files.  When using MS Access, I 
am
>>getting ODBC call failed messages quite often and I have to restart
>>Access.  On some files, I am unable to update certain fields.  For
>>example, I can't update APCINA on the APH file.  Has anyone had 
similar
>>problems?  If so, do you have any solutions?
>>
>>--Paul
>>
>>
>>>From: "Tom McKeel " <tmckeel@worldnet.att.net>
>>>Reply-To: BPCS-L@midrange.com
>>>X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)
>>>
>>>We have just upgraded our AS/400 OS to V4R2 and our Client Access was
>>>upgraded to V3R2M0 at the
>>>same time.  We have not had any problems with the Client Access 
except
>>that
>>>the BPCS Session Manager will
>>>issue an ODBC error message (when launching Order Entry) after 
>entering
>>a
>>>userid and password.
>>>
>>>The error has to do with an ODBC incompatability.  Anyone else run 
>into
>>this
>>>one?  BTW.  The CEA financials continue to work fine.
>>>
>>>
>>>
>>>+---
>>>| This is the BPCS Users Mailing List!
>>>| To submit a new message, send your mail to BPCS-L@midrange.com.
>>>| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>>>| To unsubscribe from this list send email to
>>BPCS-L-UNSUB@midrange.com.
>>>| Questions should be directed to the list owner: dasmussen@aol.com
>>>+---
>>>
>>
>>
>>______________________________________________________
>>Get Your Private, Free Email at http://www.hotmail.com
>>+---
>>| This is the BPCS Users Mailing List!
>>| To submit a new message, send your mail to BPCS-L@midrange.com.
>>| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>>| To unsubscribe from this list send email to 
>BPCS-L-UNSUB@midrange.com.
>>| Questions should be directed to the list owner: dasmussen@aol.com
>>+---
>>
>>
>>
>>+---
>>| This is the BPCS Users Mailing List!
>>| To submit a new message, send your mail to BPCS-L@midrange.com.
>>| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>>| To unsubscribe from this list send email to 
>BPCS-L-UNSUB@midrange.com.
>>| Questions should be directed to the list owner: dasmussen@aol.com
>>+---
>>
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>+---
>| This is the BPCS Users Mailing List!
>| To submit a new message, send your mail to BPCS-L@midrange.com.
>| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>| To unsubscribe from this list send email to 
BPCS-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner: dasmussen@aol.com
>+---


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.