|
Great! In that case, Walden's suggestion to use stored procedures might be exactly what you need. With stored procedures, you can write "standard" VB code that thinks it's just reading and writing to a database file, while on the AS/400 it's actually invoking RPG programs to do the work. You can have all of the business logic on the AS/400, including validations and whatnot, while keeping your VB programs nice and simple, and without spending a ton of time writing an infrastructure layer. If you were using Java, I'd suggest IBM's Java Toolbox, but for VB I think stored procedures makes the best sense. Joe > -----Original Message----- > From: midrange-l-admin@midrange.com > [mailto:midrange-l-admin@midrange.com]On Behalf Of Frank W. Kany IV > Sent: Friday, August 09, 2002 2:10 PM > To: midrange-l@midrange.com > Subject: Re: access as/400 database files w/Visual Basic 6 > > > Thanks for all your help. The reason why I want to learn how to access > AS/400 database files is becuase I'm trying to learn how to use VB as a > front end to my RPG applications. I don't know how it all works > and I want > to learn. > > Frank W. Kany IV > The Law Offices of Burr & Reid > www.burr-reid.org > ----- Original Message ----- > From: "Walden H. Leverich" <WaldenL@TechSoftInc.com> > To: <midrange-l@midrange.com> > Sent: Friday, August 09, 2002 2:53 PM > Subject: RE: access as/400 database files w/Visual Basic 6 > > > > Frank, > > > > Get a "in 21 days" book for VB that includes database access (probably > > something called ADO or Active Data Objects.) Learn this with Access or > MSDE > > as the backend database. Once you understand data access from VB to a > > database you can change the ODBC driver for Access for the one for the > > iSeries and you'll have a good start. > > > > As for Joe's comments on cross-file relationships. I would look strongly > at > > using "stored procedures" to do the updates. These SPs can be RPG (or > Cobol) > > programs on the iSeries. Of course, if you're willing to understand the > > cross-file relationships then you can issue updates from VB as well. > > > > But, first things first, learn VB data access against a local database, > then > > worry about the iSeries, it's not really any different. > > > > -Walden > > > > > > ------------ > > Walden H Leverich III > > President > > Tech Software > > (516) 627-3800 x11 > > (208) 692-3308 eFax > > WaldenL@TechSoftInc.com > > http://www.TechSoftInc.com > > > > Quiquid latine dictum sit altum viditur. > > (Whatever is said in Latin seems profound.) > > > > > > > > -----Original Message----- > > From: Frank W. Kany IV [mailto:frank.kany@burr-reid.org] > > Sent: Friday, August 09, 2002 14:19 > > To: midrange-l@midrange.com > > Subject: access as/400 database files w/Visual Basic 6 > > > > > > This is a multi-part message in MIME format. > > -- > > [ Picked text/plain from multipart/alternative ] > > I would like to LEARN how I can have my VB6 applications connect to our > > AS/400 and access data to use in my VB6 applications. I am a > beginner at > > VB6. I'm just going to write simple VB6 applications to > update/delete/write > > records to an AS/400 database file. > > > > Does anyone have any kind of pdf documents or websites that > would point me > > in the right direction? > > > > TIA, > > > > Frank W. Kany IV > > The Law Offices of Burr & Reid > > www.burr-reid.org > > -- > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@midrange.com To subscribe, > unsubscribe, > > or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > 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@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > 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@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.