Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

JDEdwards OneWorld Xe - COM Interface?

3 views
Skip to first unread message

Ryan Bruins

unread,
Aug 3, 2001, 6:35:31 PM8/3/01
to
Anyone out there come up with a simple way to interface JDEdwards COM API
(or has exprience doing it)? (or the CORBA API...could go either way)

We are embarking on a project to interface our current Delphi app. with a
new JDEdwards OneWorld Xe AS/400 system, and if anyone can point us in the
direction of tools or documentation that will help us out, it would be most
appreciated! :-)

Ryan Bruins


Jeff Clarke

unread,
Aug 6, 2001, 10:37:18 AM8/6/01
to
Good luck! We (managed) a OneWorld link here - I know my C programmer was
going crazy with the JDE documentation supplied. Granted none of us had ERP
experiece (at that time). Unfortunately I don't have any words of wisdom
for you. Just that I wish you luck.

Jeff Clarke


"Ryan Bruins" <ryanb...@deeley.com> wrote in message
news:3b6b26b6$1_1@dnews...

Jonathan Wilson

unread,
Aug 7, 2001, 10:49:26 AM8/7/01
to

I'm guessing here but, for the raw data just use ODBC or the ADO/OLEDB
provided in client access express [but get the latest PTF's/patches].
Obviously you will need to analyse the files/schema to work out the
ins and outs of the data.

If they provide a COM object running on the PC then will they supply
the details? I've often found that it is worth the extra cost of a few
days training... especially when you concider the potential cost of
getting them to do the work!

You also need to find the specifics of where the validation is
impleminted in their product... I believe the old(er) implimentations
used to validate at the program/screen level, on the AS/400. I'm
guessing that they're doing most of the validation on the AS/400,
natively... the client api just being a conduite to this...

If they do all the validation in the client things will get hary, as
you will need to re-work the validation in your application... this
has all those nasty implications when things go wrong, as they (1)
will say your program [probably] dumped dirty data into their
system... even if the problem was honestly theirs, but your
application threw it up!

I know from experience, and many scars, that once you start to
mod/link/or otherwise into a "packaged" product the issues of
ownership go out of the window... and you need to have a very good
contract, or source code, to make things work.

>
>Ryan Bruins

Jon

(1) please note that "they" is any "packaged" software provider and
does not implicitly or explicitly refer to JDEdwards!

--

Integrated 400 Solutions Ltd.

Jonathan Wilson, AS/400 consultant/director

24 Hours: 07775 638904

0 new messages