*** Original Author: ADSM-L @ MARIST - ** Remote User **; 04/14/98 07:55am
>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
> with TCP; Tue, 14 Apr 98 07:55:29 CDT
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
> with BSMTP id 2702; Tue, 14 Apr 98 08:47:31 EDT
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 4683; Tue, 14 Apr 1998 08:47:05 -0400
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8c) with NJE
> id 2470 for ADSM-L AT VM.MARIST DOT EDU; Tue, 14 Apr 1998 08:47:02
> -0400
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
> V1.2b/1.8b) with BSMTP id 4669; Tue, 14 Apr 1998 08:47:02 -0400
>Received: from ATLANTICO.mail.telepac.pt by VM.MARIST.EDU (IBM VM SMTP V2R3)
> with TCP; Tue, 14 Apr 98 08:46:56 EDT
>Received: from hobbes.6mil.pt ( 194.65.234.125 ) by ATLANTICO.mail.telepac.pt
> (Intermail v3.1 117 241) with SMTP id
> <19980414134740.OXNG1356 AT hobbes.6mil DOT pt> for <ADSM-L AT
> VM.MARIST DOT EDU>;
> Tue, 14 Apr 1998 13:47:40 +0000
>References: <5030300019635139000002L092*@MHS> <3525068A.7AE4 AT lacsd DOT org>
>X-Mailer: Forte Agent 1.5/32.451
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: quoted-printable
>Message-ID: <35365a98.6159784 AT wingate.6mil DOT pt>
>Date: Tue, 14 Apr 1998 12:46:35 GMT
>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>Sender: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>From: Rui Malheiro <rmalheiro AT MAIL.TELEPAC DOT PT>
>Organization: 6 Mil, Tecnologias de Informacao
>Subject: Re: ODBC problem
>To: ADSM-L AT VM.MARIST DOT EDU
>In-Reply-To: <3525068A.7AE4 AT lacsd DOT org>
>
Replying to: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG> (Fri, 3 Apr 1998
07:55:54 -0800)
>Mike:
>ADSM Server V3.1.0.1 - Client=3Dwin95 DB=3DMS - Access 97
>
>Here's what we're doing.
>1.Ran the ODBC setup, entered the TCP/IP address for the ADSM server
>(Same as ADSM clients use)
>
>2. Open Access- select get external data - link table - select ODBC
>databases.
>
>3. Select The ADSM 32 bit driver
>
>
>4. Get message ODBC- call failed
>
>Thanks for responding
Hi Doug,=20
I think that what may be missing is step 1 below. This is the way I did =
it:
1- Define the environment variable DSMG_DIR pointing to
<adsm_root>/ODBC/ADSM.
2- Open a new database in MS Access
3- File -> Get External Data -> Link Tables
4- Files of type: Select ODBC Databases
5- Create a new Machine Data Source (User)
6- Enter Server Name and Server Address
7- I'm prompted for Admin Name and Password
8- I get a list of tables to pick from the ADSM server.
(You can do steps 5 and/or 6 from Control Panel -> 32bit ODBC)
One problem I have is that when I close MS Access *after* using ADSM ODBC=
I
get an Aplication Exception Error.=20
--
Rui Malheiro,
Rui Malheiro,
6 Mil - Tecnologias de Informacao
URL: <http://www.6mil.pt/>
*** Comments From: STEWAJM - Stewart, Mike; 04/14/98 08:45am
I didn't have much problems getting to the server (MVS 3.1)
from NT/Access 97. However, I find that link tables
only give me a subset of the data. For example, the
volumes table only gives me the first 150 rows.
Maybe there is some limit I've missed somewhere on the
client end.
A pass-through SQL request will give all the rows.
|