|
I didn't understand it either, Jim. But a co-worker of mine just gave it a try, and after that update it worked ! Must have been some .DLLs hanging around in the system32 directory ... We did not have the problem on machines WITHOUT CA Express, though. (Be it Win2000 SP2 or SP3 or NT 4 SP6a, all the same) Regards from Germany, Philipp Jim Franz schrieb: > > what's the ptf level of your Client Access version ? > > We had a similar problem with a VB-program pulling > > data from a V5R1 machine, when we did upgrade the > > PC's to ClientAccess V5R1 (before: V4R5) AND installed > > the latest ptf for CA Express, the problem went away. > I'm trying to understand this. My understanding was that Client > Access software on pc was not used if this is a pc program (Excel) > accessing the IFS thru a netserver share. We know the CA on these > machines is older (V4R5 and down 3 svc packs) but assumed it could > not be part of the problem. > jim > > ----- Original Message ----- > From: "Philipp Rusch" <Philipp.Rusch@xxxxxxxxxxxx> > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > Sent: Tuesday, April 01, 2003 2:46 AM > Subject: Re: v4r5 netserver excel problem > > > Jim, > > what's the ptf level of your Client Access version ? > > > > We had a similar problem with a VB-program pulling > > data from a V5R1 machine, when we did upgrade the > > PC's to ClientAccess V5R1 (before: V4R5) AND installed > > the latest ptf for CA Express, the problem went away. > > > > HTH, Philipp Rusch > > > > Jim Franz schrieb: > > > > > I have several new pc's with Win 2000 Pro Svc pack 3. > > > AS400 V4r5 with cume C2169450 > > > MS Excel cannot get a doc from the IFS. Get error msg > > > "not enough avail memory or disk space. Machines have plenty of both. > > > (256 meg memory 40 gig hard drive) > > > Existing pc's with Svc pack 2 work fine. > > > Is there possibly an AS400 ptf or fix? > > > have searched and not found anything. > > > PC's all came preloaded Svc Pack 3. > > > jim > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.