RE: OLEgen

The other option is to use the .tlb file or the prog id in your
registry. Just type in 'c:\apps\forte\install\bin\olegen', it
should give you all the options.
ka
From: Alan Ho[SMTP:[email protected]]
Sent: Wednesday, August 13, 1997 11:28 AM
To: Forte Users
Subject: OLEgen
Subject: OLEgen 8/13/97 9:25 AM
Referring to p. 215 of the "Integrating with external systems" manual I am
trying to perform step one of the generation. Step 1 is to run the olegen
utility. I tried to run from the Start menu but it doesn't seem to work.
The command line I typed in is as follows:
"c:\apps\forte\install\bin\olegen -it c:\program files\excel\excel -of
c:\program files\excel.pex"
The first segment is the name of the file to run. The -it is the file name
to generate pex code for. -of is the output file name.
Is the specification incorrect? It tells me to make sure path and filename
are correct and all required libraries are available.
Internet: [email protected]

De: Diemmi Davide <[email protected]>
A: '[email protected]' <[email protected]>
CC: Sidoli Paolo <[email protected]>; Vezzani Gabriella
<[email protected]>
Asunto: OLE and Excel97
Fecha: jueves 27 de noviembre de 1997 17:58
Hi everybody,
we're porting our OLEGen-erated code for Excel95 to Excel97 noticing
that with F3 the OLE library has deeeply changed. In particular, we're
getting in troubles "guessing" which settable variable must be set to
reference an arbitrary Excel cell once a Worksheet has been opened and
its default activecell (top-left corner) has been filled.
Any suggestion about how to move to another cell? Shall we address the
Application, the Workbooks or the Range virtual-attributes to achive
that?
[deleted]
May be the following can help you, although we only have been successful in
communicating with Excel 5.0. The same program did not work with Excel97.
For accesing an arbitrary cell we use:
-- This inserts a string named etiqueta into cell A2
Range.SetDispatchObject (Worksheet2.Cells (VariantI2 (value = 2, mechanism=
VARIANT_INOUT),VariantString(value='A',mechanism=VARIANT_INOUT)));
Range.Value = VariantString (value=etiqueta);
Regards,
Jesus Zamarreno
EAM Sistemas Inform&aacute;ticos S.L.
C/ Padre Llanos, 33 47014 Valladolid
Tlf.: +34 83 352922 Fax: +34 83 352115
e-mail: [email protected]

Similar Messages

  • OLEGEN (Re: OLE integration)

    OLEGEN can be run in different ways -
    using the type library : (not available for Word)
    Example : For Excel
    olegen -it xlen50.olb -of excel.pex -op Excel
    using the ProgID (most commonly done)
    Example : For Word
    olegen -ip Word.Basic -op Word -oc Application -of word.pex
    using CLSID
    Example : For Word
    olegen -ic {000209FE-0000-0000-C000-000000000046) -op Word -oc Application -of Word.pex
    NOTE :This should be run from Windows Run if it is Win 3.1 or WFWG.
    Dear Sir,
    Thank You for Your kind help with the real example of Forte-OLE
    interface. It helps to us a lot.
    If it will be possible, please, answer for two simple questions:
    1. On what file we need to run OLEGEN utility (probably with OLB
    extension) to receive WORD.PEX file (WORD project).
    2. Does anybody tried to do the same with CDispatch? If yes,
    what are the results, cause I tried with it and still have no success and I
    can not understand why.
    Sincerely Yours,
    Pavel Ryzhkov

    OLEGEN can be run in different ways -
    using the type library : (not available for Word)
    Example : For Excel
    olegen -it xlen50.olb -of excel.pex -op Excel
    using the ProgID (most commonly done)
    Example : For Word
    olegen -ip Word.Basic -op Word -oc Application -of word.pex
    using CLSID
    Example : For Word
    olegen -ic {000209FE-0000-0000-C000-000000000046) -op Word -oc Application -of Word.pex
    NOTE :This should be run from Windows Run if it is Win 3.1 or WFWG.
    Dear Sir,
    Thank You for Your kind help with the real example of Forte-OLE
    interface. It helps to us a lot.
    If it will be possible, please, answer for two simple questions:
    1. On what file we need to run OLEGEN utility (probably with OLB
    extension) to receive WORD.PEX file (WORD project).
    2. Does anybody tried to do the same with CDispatch? If yes,
    what are the results, cause I tried with it and still have no success and I
    can not understand why.
    Sincerely Yours,
    Pavel Ryzhkov

  • ActiveX problems with 3.0.F.2 (fwd)

    This is the message I sent to tech support. Has anyone else seen this
    type of thing? Any suggestions (even half-baked) would be appreciated.
    -- Adam
    ---------- Forwarded message ----------
    Date: Tue, 17 Mar 1998 13:48:17 -0600 (CST)
    From: Adam Mckee <[email protected]>
    To: [email protected]
    Subject: ActiveX problems
    Product: Forte
    Version of Forte: 3.0.F.2
    Server OS: HPUX
    Client OS: NT/Win 95
    DBMS: Oracle
    Reproducible(?): Yes
    Brief description of issue:
    I have experienced problems using ActiveX controls. I have tried several
    controls, including:
    o Microsoft Forms 2.0 SpinButton
    o Microsoft Forms 2.0 CheckBox
    o Microsoft Forms 2.0 EditBox
    o AddSoft Gantt/OCX
    o Sheridan MonthView
    o Sheridan DayView
    o Sheridan DateCombo
    o Microsoft Calendar Control
    (specifically mentioned in a Forte technote)
    I have experienced problems with all of these controls. With the Sheridan
    DateCombo, the Forte environment crashes when I attempt to drop the
    control into a form using the "Insert Control..." button. Before the
    environment crashes, I get a series of informational and error dialog
    boxes as follows:
    o error: unexpected exception -10737415717
    o error: The Error Manager stack is empty (repeated 3 times)
    o information: the workspace is now read-only because the
    repository is disabled.
    o error: Exception escaped from terminating task CW.Display
    o ERROR: TMgr.Terminate: fatal error terminated partition
    With all the other controls I tried, the ActiveX support appears to work
    properly until I attempt to bind an instance of the olegen-generated
    class to the control itself in the window's Init() method:
    --- MyWindowClass.Init() ----
    super.Init();
    myActiveXControl = new();
    After this has been done, the Forte environment may "hang" when I interact
    with the control at run-time. For example, each time a generate a mouse
    event inside the control, I risk hanging the Forte environment. I might
    be able to interact with the control 50 times before the environment
    hangs, or it might hang after a single mouse click. Until the crash/hang
    occurs, the ActiveX support appears to work properly: I am able to trap
    mouse events, and interact with the control using the provided interface.
    Any help or advice you can offer would be appreciated. I would be happy
    to provide any additional information you may require.
    -- Adam McKee

    I don’t recall any problems importing to “selected item’ which I always use so I define where it goes and what it’s called.
    Do you have Aperture’s Activity Window open so you can see where it is hanging up? Is it just busy generating Previews etc.? I know it sounds more serious than just ‘busy’ but would be interesting to know what it’s doing then.
    After these problems, assuming that previews and thumbnails are generated correctly, it may be a good precaution to restart Aperture while holding down the OPTION and COMMAND keys so you can Repair Permissions or Repair the database. Even rebuilding the database is fairly quick if those first two options are ineffective.

  • RE: Validating XML message...

    Actually I stand corrected. XML Spy does seem to provide an OLE API to XML
    validation ( the isValid method on the IDocument class ) although I haven't
    tested it yet.
    In my previous post I was thinking of another XML product I tested earlier
    in the week which did not.
    -----Original Message-----
    From: Shaughnessy, Kevin
    Sent: Friday, April 20, 2001 08:59
    To: 'Rumen Georgiev'
    Cc: [email protected]
    Subject: RE: Validating XML message...
    Rumen,
    One idea that is possible is to use an OLE interface to a 3rd party XML
    product. This assumes your logic which needs to validate is running on a
    Windows box. But if so, it may work. Many products have type libraries which
    can be run through OLEGen to create Forte classes. Then you can use TOOL to
    talk OLE to that product.
    For example, XML Spy 3.5 has a type library from which I created a Forte
    project. Unfortunately this product didn't offer any extra features than
    Forte's XMLParser ( i.e. the API didn't allow me to validate the XML ) so I
    am back to using Forte's parser until I can test another product. If you
    find one that does what you want let me know.
    I've used OLE a lot with Forte to get functionality from other products (
    VISIO, MS Office ) that Forte doesn't provide and it works well. Its a
    platform dependent solution but one that may work for you.
    Kevin
    -----Original Message-----
    From: Rumen Georgiev [mailto:[email protected]]
    Sent: Friday, April 20, 2001 07:21
    To: [email protected]
    Cc: [email protected]
    Subject: RE: Validating XML message...
    Hi Kevin,
    From the answers I've got it seems Forte parser is anon-validating one. So we have to look for an external
    tool to validate these messages. What I am concerned
    about is the integration with Forte.
    Thanks for your help!
    Rumen
    Rumen,
    From Tech Note 11811:
    "ParserFactory.makeParser() will return a default,
    non-validating XML parser."
    My experience is that Forte's default XML parser will
    not validate but will throw an exception if the XML
    document is not well formed. I'm using the DOM
    model and this exception happens on the
    Document.importDocument( ) method.
    If you want anything more than that you'll have to do
    it externally.
    Kevin-----Original Message-----
    From: Rumen Georgiev [mailto:[email protected]]
    Sent: Thursday, April 19, 2001 11:49 AM
    To: [email protected]
    Subject: Validating XML message...
    We have to validate inbound XML messages before
    processing them. The guys on the other side are
    following XMLSchema recommendations to create their
    messages using xsd file for validation. We plan to
    use XMLParser Forte library and as far as I know it
    validates against dtd file (haven't tried yet). If
    this is true we have two options:
    1. Find a program to convert xsd into dtd file and
    use Forte XMLParser for validation.
    2. Validate the message beforehand with an external
    tool. That means integration between Forte and this
    tool.
    I would appreciate any help with either approach. Do
    you know of a program doing xsd into dtd? Have you
    used any existing tool on the market to validate
    using XMLSchema? Or may be there is another solution
    to
    this?
    Thank you in advance,
    Rumen
    =====
    Rumen Georgiev
    Forte Developer
    EXE Technologies
    (610) 872-4400 Ext.222
    Do You Yahoo!?
    Yahoo! Auctions - buy the things you want at great prices
    http://auctions.yahoo.com/

    Hi,
    there is some change in the XMLSPy4.3/XMLType Library 1.2 :
    Validation
    One common task on documents is to validate them against an assigned schema or DTD. If the XML file has no schema or DTD already assigned, use "Document.AssignSchema" or "Document.AssignDTD" to add the necessary references to the document.
    Examples:
    objSpy.ActiveDocument.AssignSchema "C:\mySchema.xsd", False
    or
    objSpy.ActiveDocument.AssignDTD "C:\myDTD.dtd", False
    If you want the user to select a schema or DTD, pass True as the second parameter to these functions to display a file-dialog. These methods only put the reference into the document and do not check the existence of the specified file. If the file path is not valid, the validation will fail.
    After you have assigned a valid schema or DTD reference to your file, you are able to validate it with "Document.IsValid". IsValid needs some out-parameters that must be declared as VARIANTs to be accessible from script languages like VBScript and JavaScript.

  • Problems moving distribution from one environment toanother

    Hi all,
    Problems moving distribution from one environment to another
    Initially we have the environment as below:-
    Production :-
    Server1 : AIX Environment manager (dealing with conductor, web, db)
    Server2 : NT Node manager (dealing with outlook)
    Development :-
    Server3 : NT Environment manager (dealing with conductor, web, db)
    Server4 : NT Node manager (dealing with outlook)
    Currently, we intended to change the production environment via
    changing the Server1 to Server3, as the new environment
    manager, while the node manager unchanged.
    Things that we've done in Server2, the node manager for
    production environment:-
    1) Pointing to Server3 instead of Server1, by changing Forte
    Control Panel and changing registry entry.
    2) Re-deploy the needed libraries in the new environment, so
    that it can has the updated version.
    3) Re-olegen the vb component.
    4) Re-deploy the whole application.
    However, we're facing the following problems/error messages
    for the newly deployed Forte application:
    1) Failed to bind to object named (/wfuseraccessobj/odbso/1)
    2) Failed to bind to object named (/wfuseraccessobj/emailso/1)
    These errors are actually refer to the libraries that used by
    Conductor in order to perform database retrieval, and emailing
    functions. These functions were worked properly in the initial
    environments.
    NOTE: The first error could be okay when refreshing the internet browser
    (as our system is a web-based system), somehow it keeps on occurring every
    now and then.
    Please advice on this matter and reply ASAP as the project
    delivery is crucial for our side.
    Errors:
    ERROR 1:
    registering agent anchor /WorkFlow/centrale/lmseng/Agents/EngineUnit_Unit1
    Attached to manager for node CHARON.
    23-Nov-1999 17:38:32: EngineShell.SetEngine: Unit1: changing engine state
    to
    ONLINE
    23-Nov-1999 17:38:32: EngineShell.SetEngine: Unit1: trying to remove old
    shell anchor
    23-Nov-1999 17:38:32: EngineShell.SetEngine: Unit1: creating engine object
    23-Nov-1999 17:38:32: EngineShell.SetEngine: Unit1: engine object created
    23-Nov-1999 17:38:32: EngineShell.SetEngine: Unit1: attaching database
    service
    23-Nov-1999 17:38:33: EngineShell.SetEngine: Unit1: connected to database
    23-Nov-1999 17:38:33: EngineShell.SetEngine: Cold-starting engine... 0
    23-Nov-1999 17:38:35: EngineShell.SetEngine: Unit1: registering shell
    anchor
    23-Nov-1999 17:41:31: Build: Exception raised of type ProtectionException
    and severity 3: An user exception caught in ValidateUser().
    23-Nov-1999 17:41:33: Build: Exception raised of type ProtectionException
    and severity 3: An user exception caught in ValidateUser().
    23-Nov-1999 17:41:34: Build: Exception raised of type ProtectionException
    and severity 3: An user exception caught in ValidateUser().
    23-Nov-1999 17:41:34: Build: Exception raised of type ProtectionException
    and severity 3: An user exception caught in ValidateUser().
    23-Nov-1999 17:42:54: Build: Exception raised of type ProtectionException
    and severity 3: An user exception caught in ValidateUser().
    23-Nov-1999 17:42:56: Build: Exception raised of type ProtectionException
    and severity 3: An user exception caught in ValidateUser().
    ERROR 2:
    registering agent anchor /WorkFlow/centrale/lmseng/Agents/EngineUnit_Unit1
    Attached to manager for node CHARON.
    13-Oct-1999 16:45:40: EngineShell.SetEngine: Unit1: changing engine state
    to
    ONLINE
    13-Oct-1999 16:45:40: EngineShell.SetEngine: Unit1: trying to remove old
    shell anchor
    13-Oct-1999 16:45:40: EngineShell.SetEngine: Unit1: creating engine object
    13-Oct-1999 16:45:40: EngineShell.SetEngine: Unit1: engine object created
    13-Oct-1999 16:45:40: EngineShell.SetEngine: Unit1: attaching database
    service
    13-Oct-1999 16:45:43: EngineShell.SetEngine: Unit1: connected to database
    13-Oct-1999 16:45:43: EngineShell.SetEngine: Cold-starting engine... 0
    13-Oct-1999 16:45:47: EngineShell.SetEngine: Unit1: registering shell
    anchor
    13-Oct-1999 16:49:58: Build: Exception raised of type ActivityException and
    severity 3: A TOOL execution exception caught in ReadyAction().
    13-Oct-1999 16:49:58: Build: Exception raised of type ActivityException and
    severity 3: Exception in activity TempReview (4) will cause an abort of
    process LMSPD (10).
    SYSTEM ERROR: Exception in activity TempReview (4) will cause an abort of
    process LMSPD (10).
    Class: ErrorException
    Error #: [2, 122]
    Detected at: OfferedActivity.Activity.AbortProcessInException()
    Error Time: Wed Oct 13 16:49:58
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    INFORMATION: Stack Trace for Exception:
    No 4gl Traceback
    Class: qqsp_ErrorDescriptor
    Error Time: Wed Oct 13 16:49:58
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    SYSTEM ERROR: A TOOL execution exception caught in ReadyAction().
    Class: ErrorException
    Error #: [2, 107]
    Detected at: OfferedActivity.ReadyAction
    Error Time: Wed Oct 13 16:49:58
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    INFORMATION: Stack Trace for Exception:
    No 4gl Traceback
    Class: qqsp_ErrorDescriptor
    Error Time: Wed Oct 13 16:49:58
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    SYSTEM ERROR: The attribute firstReviewerID is not available in this
    accessor.
    Class: qqsp_UsageException with ReasonCode: SP_ER_PARAMETERERROR
    Error #: [15, 1206]
    Detected at: AttributeAccessor.AttributeAccessor.Find()
    Last TOOL statement: method TempReview.OnReady
    Error Time: Wed Oct 13 16:49:58
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    Begin Stack Backtrace
    ==========================================================
    Trace caused by a segmentation or access violation in the Forte executable:
    Application: WFEngineUnit_cl1
    Platform: PC / NT
    Partition: WFEngineUnit_cl1_Part1
    Generated: 02-Jun-1998 19:10:20
    By: ftexec Version 3.0.G.2
    Fault at 13-Oct-1999 16:49:58, pid '2441', node 'CHARON':
    User Name: SYSTEM
    Machine Name: CHARON with 2 CPU(s)
    OS version 4.0
    Loading symbols for ...
    d:\forte\install\bin\QQCT.dll
    d:\forte\install\bin\QQSH.dll
    d:\forte\userapp\wfengine\cl1\wfengi1.exe
    d:\forte\install\bin\QQKN.dll
    d:\forte\install\bin\QQSM.dll
    d:\forte\install\bin\QQDO.dll
    d:\forte\install\bin\QQCM.dll
    d:\forte\install\bin\QQRT.dll
    d:\forte\userapp\ofcustom\cl0\libofcus.dll
    d:\forte\install\bin\QQHD.dll
    d:\forte\install\bin\QQDB.dll
    d:\forte\install\bin\QQDS.dll
    d:\forte\install\bin\QQDD.dll
    d:\forte\userapp\wfcustom\cl0\libwfcus.dll
    d:\forte\userapp\wfenvdef\cl1\libwfenv.dll
    d:\forte\install\bin\QQEM.dll
    d:\forte\install\bin\QQFO.dll
    d:\forte\install\bin\qqtlnt.dll
    d:\forte\install\bin\w3tpwss.dll
    C:\WINNT\System32\rpcltc1.dll
    C:\WINNT\System32\comctl32.ocx
    d:\forte\install\bin\QQRP.dll
    C:\WINNT\System32\OLEPRO32.DLL
    C:\WINNT\System32\WINSPOOL.DRV
    C:\WINNT\System32\MFC40.DLL
    C:\WINNT\system32\OLEAUT32.dll
    C:\WINNT\System32\rnr20.dll
    C:\WINNT\System32\IMM32.dll
    C:\WINNT\system32\msafd.dll
    C:\WINNT\System32\wshtcpip.dll
    C:\WINNT\System32\WS2HELP.dll
    C:\WINNT\System32\WS2_32.dll
    C:\WINNT\System32\WSOCK32.dll
    C:\WINNT\System32\MSVCRT40.dll
    C:\WINNT\system32\COMCTL32.dll
    C:\WINNT\system32\ole32.dll
    C:\WINNT\system32\SHELL32.dll
    C:\WINNT\system32\comdlg32.dll
    C:\WINNT\system32\ADVAPI32.dll
    C:\WINNT\system32\RPCRT4.dll
    C:\WINNT\system32\USER32.dll
    C:\WINNT\system32\GDI32.dll
    C:\WINNT\system32\KERNEL32.dll
    C:\WINNT\System32\ntdll.dll
    C:\WINNT\system32\MSVCRT.dll
    C:\WINNT\System32\MSVCIRT.dll
    Stack backtrace ...
    wfengi1 004edd89 (017bb4f0,019e85e0,046bfe34,016a0c08)
    wfengi1 004e29d1 (017bb4f0,019f1fc0,00000000,00f039d0)
    wfengi1 004e2ecb (017bb4f0,00000024,019e85e0,019f1f98)
    wfengi1 004e4503 (017bb4f0,019e85e0,01a20025,01a22868)
    QQKN 005dc66f (017bb4f0,019e85e0,019f0025,01a22848)
    QQKN 005df7a5 (017bb4f0,019e85e0,01a22890,01a22848)
    QQKN 00697109 (017bb4f0,00000000,00f039d0,00f039d0)
    QQSH 0027c47b (017bb4f0,0161b9d8,00000000,017bb4f0)
    QQKN 0067f24f (01619c14,017bb4f0,f34a8eb8,046bffb8)
    QQKN 0067e2d5 (01619c14,00000000,00000000,00f039d0)
    MSVCRT 780099ed (00f039d0,00000000,00000000,00f039d0)
    KERNEL32 77f04f2c (78009990,00f039d0,00000000,00905a4d)
    QQCT 00000000 (00000000,00000000,00000000,00000000)
    End of Stack Backtrace
    =========================================================
    13-Oct-1999 16:50:10: Build: Exception raised of type TimerException and
    severity 3: Exception in timer OneWorkingDayTimer (3) will cause an abort
    of
    process LMSPD (10).
    SYSTEM ERROR: Exception in timer OneWorkingDayTimer (3) will cause an abort
    of process LMSPD (10).
    Class: ErrorException
    Error #: [8, 111]
    Detected at: ElapsedTimer.PTimer.FinishExpiration()
    Error Time: Wed Oct 13 16:50:10
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    INFORMATION: Stack Trace for Exception:
    No 4gl Traceback
    Class: qqsp_ErrorDescriptor
    Error Time: Wed Oct 13 16:50:10
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    FATAL ERROR: System segmentation/access violation caught.
    Class: qqos_SystemException
    Error #: [101, 321]
    Detected at: qqos_MainExFilter at 1
    Error Time: Wed Oct 13 16:50:10
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    ERROR: qqlo_LomTaskInitiator::Run: Asynchronous task exiting:
    The following error was not on the error stack:
    FATAL ERROR: System segmentation/access violation caught.
    Class: qqos_SystemException
    Error #: [101, 321]
    Detected at: qqos_MainExFilter at 1
    Error Time: Wed Oct 13 16:50:10
    Exception occurred (locally) on partition "WFEngineUnit_cl1_Part1",
    (partitionId = E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913, taskId =
    [E3C2D7C0-5934-11D3-A63F-EB531FA4AA77:0x913.138]) in application
    "WFEngineUnit_cl1", pid 2441 on node CHARON in environment centrale.
    ERROR: TMgr.Terminate: fatal error terminated partition

    Lori,
    Yes. I organize all my film rolls by name. If I import new pictures that don't fit into an existing film roll name I create a new film roll with a name appropriate to the theme of the new pictures. No problem with this.
    However, if I import pictures at a later date that I want to move to an existing film roll, there is a problem if scrolling is required to bring the existing film roll into view in the display pane.
    For example, I have a film roll called "Flowers & Plants". I later import a roll that contains some pictures that I want to move to the Flowers & Plants roll. The Flowers & Plants roll is not visible in the display pane so scrolling is necessary. I select and drag the new pictures up (the new film roll is always at the bottom of the display pane) to reveal the Flowers & Plants film roll. However, the film rolls scroll by so fast it is virtually impossible to stop on the Flowers & Plants roll's title bar.
    This was not a problem with earlier versions of iPhoto on slower Macs. I really appreciate the much improved iPhoto/Mac performance but I wish there were some way to control this aspect.
    I hope this helps.
    Thanks.
    Mike

  • RE: Report writers

    >
    Dear Pascal,
    Hi. I am Mohan, working on Forte. We too are trying to use Crystal
    reports as an OLE server. I am able to specify the report name to print
    but unable to view the report.
    Here are the steps followed by me.
    1) Crystal Reports was installed.
    2) Olegen was run on command prompt. I got the following messages.To be perfectly honest, I don't know much about this. Another person of
    our team was responsible for this. He was able to get this working, I
    had other responsibilities. I could ask him however. I'll see if I can
    come up with a decent answer.
    Luck,
    Pascal Rottier
    Origin Netherlands/Rotterdam

    Please check the following links
    Report Painter/Writer
    report painter and report writer
    Regards,
    Rajesh Banka
    Reward suitable points.
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

  • Word OLE problems

    I've just olegen'd Word, 97 and I have got myself a project that won't
    compile
    because GetProperty is used with the wrong argument signatures. I used
    the
    3.0.G.2 olegen, because that is what we are using of the desktop.
    However, on the
    server we are still 3.0.E.? I think, and I see that a problem with
    OleGen & Word 97
    was fixed in 3.0.F.2 (Bug 32391). Are we stuck with this until we
    upgrade the server?
    I also wonder why the Word project that is currently there is
    significantly different
    from my Word project (oddly enough the things that don't compile aren't
    in the old
    project, so I'm guessing that someone before me found this problem too).
    Is there a solution out there?
    Thanks
    Jamie Anstice
    Programmer / Analyst
    University of Canterbury
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Can't you open it using the same mechanism you use for retrieving Word docs ?
    If the "OLE Class" item property is blank then you can insert any type of document into your OLE container.
    If your OLE container is a base table item then "OLE Activation Style" item property is "Double click" or Focus IN" then you can view the item by navigating or double clicking on the OLE container.
    Does your OLE Container show anything, e.g. a PDF icon when you have inserted the PDF file ?
    If PDFs are still not loading then check the list of OLE classes that Forms is showing in the drop down list for the OLE CLass property. All the ADOBE ones start with "ADO" or "adobe".

  • Word 97

    We've recently changed to the Office 97 suite & are having some problems with
    apps that startup Word. They startup fine but when you shutdown the Forte
    app, it doesn't shutdown Word? This used to work for Word 95?? Do we have to
    run the OLEGEN utility again to bring in any changes for Word 97?
    Any comments/suggestions would be appreciated.
    Doug Scurr
    Information Services
    Piper Jaffray Companies
    [email protected]
    (612) 342-1748
    If you are not the intended recipient, please notify the Sender.
    Non-business opinions may not reflect opinions of Piper Jaffray
    Companies (PJC). Distribution or other use of this information
    is prohibited without written consent from the author.
    PJC reserves the right to monitor all e-mail.
    ------------------------------------------------------------------------------

    Hi, I was wondering if liam was able to get an answer to his question because I am having the exact same problem. I was emailed a 97-04 Word document but Pages is telling me it cannot open it because of an invalid format. I am a (very) new user and don't know if I'm just doing something wrong? Any suggestions anyone could offer would be appreciated!
    Thanks,
    Lisa

  • OLE automation

    Auteur : Corinne Ribeyre-F085785 &agrave; _CARPO04
    I need help with OLE Automation implementation (Excel,
    CrystalReport,Word ...)
    I generate Excel project with OleGen but no documentation exist for
    this project. So I made severals tests (with Excel).
    I can do (see examples):
    - open a file
    - open Excel Application
    - open WorkBook, WoorkSheet
    - Write and Read a Cell (but I am not sure it's the more efficient
    method to do this)
    - run a macro with parameters
    But, I CAN'T do:
    - run a command with parameters like PivotTableWizard (tableau croise
    dynamique)
    Does a Documentation exist about Forte project generated by Olegen
    Tool (Excel..) ?
    Does a Documentation exist about Forte/Crystal Report ?
    Thank You for all answers and examples,
    Corinne
    Examples
    -- Open Excel
    theApplication : Excel . Application = New;
    theApplication . CreateUsingProgID(NX('excel.application'));
    --- Excel Visible /not visible
    theApplication . Visible = VariantBoolean(Value = False);
    -- Get all WorkBooks of Excel Application
    theWorkBooks : Excel . WorkBooks = New;
    theWorkBooks . SetDispatchObject(theApplication . Workbooks());
    -- Open File.xls (added with previous Application)
    theWorkBooks . Open (VariantString(Value = 'C:\\temp\\File.xls'));
    -- Link file with a WorkBook
    aWorkBook : Excel . WorkBook = New;
    aWorkBook . SetDispatchObject(theApplication .
    Workbooks(VariantString(value='File.xls')));
    -- Link a Folder (Sheet1) from File with WorkSheet
    aWorksheet : Excel . Worksheet = New;
    aWorksheet . SetDispatchObject(aWorkBook .
    Worksheets(VariantString(value='Sheet1')));
    aRange : Excel . Range = New;
    -- Fill Cell (1,1) with 'Article'
    TitreArt : VariantString = VariantString(Value = 'Article');
    aRange . SetDispatchObject(aWorksheet . Cells(VariantInteger(Value =
    1), VariantInteger(Value = 1)));
    aRange . Value = titreArt;
    -- Fill Cell (1,2) with 'Date'
    TitreDate : VariantString = VariantString(Value = 'Date');
    aRange . SetDispatchObject(aWorksheet . Cells(VariantInteger(Value =
    1), VariantInteger(Value = 2)));
    aRange . Value = TitreDate;
    -- Run a Macro
    theApplication . Run(VariantString(Value = NX('MacroName')),
    VariantInteger(Value = 65),
    VariantInteger(Value = 7));
    -- Page Setup
    -- Link a Folder (Sheet2) from File with WorkSheet
    aWorksheet . SetDispatchObject(aWorkBook .
    Worksheets(VariantString(value='Sheet2')));
    aPageSetup : Excel . PageSetUp = New;
    aPageSetup . SetDispatchObject(aWorksheet.PageSetup);
    aPageSetup . PrintTitleRows = VariantString (Value = '');
    aPageSetup . PrintTitleColumns = VariantString (Value = '');
    aPageSetup . LeftHeader = VariantString (Value = 'MICKEY');
    aPageSetup . CenterHeader = VariantString (Value = 'MOUSE');
    aPageSetup . RightHeader = VariantString (Value = '&J &H'); --
    Attention J H en Excel Fran&ccedil;ais; D T en Anglais
    aPageSetup . LeftFooter = VariantString (Value = '');
    aPageSetup . CenterFooter = VariantString (Value = 'DISNEYLAND
    PARIS');
    aPageSetup . RightFooter = VariantString (Value = '&P / &T');
    aPageSetup . LeftMargin = VariantInteger(Value = 1);
    aPageSetup . RightMargin = VariantInteger(Value = 1);
    aPageSetup . TopMargin = VariantInteger(Value = 1);
    aPageSetup . BottomMargin = VariantInteger(Value = 1);
    aPageSetup . HeaderMargin = VariantDouble(Value = 0.5);
    aPageSetup . FooterMargin = VariantDouble(Value = 0.5);
    aPageSetup . PrintHeadings = VariantBoolean(Value = False);
    aPageSetup . PrintGridlines = VariantBoolean(Value = False);
    aPageSetup . PrintNotes = VariantBoolean(Value = False);
    aPageSetup . CenterHorizontally = VariantBoolean(Value = True);
    aPageSetup . CenterVertically = VariantBoolean(Value = True);
    aPageSetup . Orientation = VariantInteger(Value = 2); --
    (1:xlPortrait, 2:xlLandscape)
    aPageSetup . Draft = VariantBoolean(Value = False);
    aPageSetup . PaperSize = VariantInteger(Value = 9);
    -- (8: xlPaperA3, 9: xlPaperA4)
    aPageSetup . FirstPageNumber = VariantInteger(Value = -4105);
    -- xlAutomatic
    aPageSetup . Order = VariantInteger(Value = 1);
    -- xlDownThenOver
    aPageSetup . BlackAndWhite = VariantBoolean(Value = True);
    aPageSetup . Zoom = VariantBoolean(Value = False);
    aPageSetup . FitToPagesWide = VariantInteger(Value = 1);
    aPageSetup . FitToPagesTall = VariantInteger(Value = 1);
    -- Save File
    aFilename : VariantString = VariantString(Value =
    NX('C:/Temp/Essai.xls'));
    aWorkBook . SaveAS(FileName = aFilename);
    -- Print File
    PrintOptions : PrintOptionsDesc;
    PrintOptions = Self . Window . WindowSystem . DefaultPrintOptions .
    Clone (Deep = True);
    If (self.Window.PrintDialog (PrintOptions= PrintOptions,
    ShowSetupDialog = TRUE,
    ShowJobDialog = FALSE) = BV_OK) Then
    aWorksheet . PrintOut();
    End If;
    -- Unlink
    aWorkBook . RunAutoMacros(VariantInteger(Value = 2)); --xlAutoFermer 
    -- Cf doc VBA
    aWorkBook . Close(variantboolean (Value = False));
    TheApplication . Quit();
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi all, forget this silly question...
    I studied a little bit and learned how to handle OLEs properly...
    Many thanks

  • Excel OLE problems

    Can anyone provide information on how to call the different methods on an
    Excel. object.
    We used OLEgen to create the PEX file for Excel. However, when I try to invoke
    the Opentext method on the Excel.Application.Workbooks class, I keep getting an
    'OpenText method for Workbooks failed' message. I had the same problem with
    the VB code that was doing this same thing but was able to resolve it by going
    to TOOLS-REFERENCES, and adding the Excel Library, but I don't know how to add
    this reference in Forte.
    self.Open();
    event loop
    when task.Shutdown do
    exit;
    when <myButton>.click do
    ExcelApp : Excel.Application = new;
    ExcelApp.CreateUsingProgID('Excel.Application');
    NamedParams : array of NamedParameter = new;
    NamedParams.appendrow(
    NamedParameter(Name = 'filename', value =
    variantstring(value='C:\WINDOWS\TEMP\excel2.txt')));
    NamedParams.appendrow(
    NamedParameter(Name = 'Origin', value = variantstring(value='xlWindows')));
    NamedParams.appendrow(
    NamedParameter(Name = 'Tab' , value = variantboolean(value=True)));
    NamedParams.appendrow(
    NamedParameter(Name = 'Comma', value = variantboolean(value=True)));
    tdMethodName : textdata = new;
    tdMethodName.setvalue('OpenText');
    ExcelApp.Workbooks.InvokeMethod(MethodName = tdMethodName, params =
    namedparams);//(filename=variantstring(value='C:\WINDOWS\TEMP\excel2.txt'),Origin=variantstring(value='xlWindows'),StartRow=varianti2(value
    = 1),DataType=variantstring(value='xlDelimited')
    ,TextQualifier=variantstring(value='xlDoubleQuote'),
    ConsecutiveDelimiter=variantboolean(value=False),Tab=variantboolean(value=True),Semicolon=variantboolean(value=False),Comma=variantboolean(value=True),Space=variantboolean(value=False),Other=variantboole
    an(value=False));
    end event;

    REPORT zr_and_d.
    DATA: K_LST LIKE ABAPLIST OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN OF k_L,
          LINE(120),
          END OF k_L.
    DATA: TLX LIKE k_L OCCURS 0 WITH HEADER LINE.
    DATA V_SHEET_NAME LIKE RLGRAP-FILENAME.
    PARAMETERS: P_FNAME LIKE RLGRAP-FILENAME,
                P_DATUM LIKE SY-DATUM.
    SUBMIT ZTEST
            WITH DATUM EQ P_DATUM
            EXPORTING LIST TO MEMORY AND RETURN.
    CALL FUNCTION 'LIST_FROM_MEMORY'
         TABLES
              LISTOBJECT = k_LST.
    CALL FUNCTION 'LIST_TO_ASCI'
         TABLES
              LISTASCI           = TLX
              LISTOBJECT         = k_LST
         EXCEPTIONS
              EMPTY_LIST         = 1
              LIST_INDEX_INVALID = 2
              OTHERS             = 3.
    IF SY-SUBRC EQ 0 AND NOT k_LST IS INITIAL.
      CONCATENATE 'ZTEST' P_DATUM INTO V_SHEET_NAME.
      CALL FUNCTION 'EXCEL_OLE_STANDARD_DAT'
           EXPORTING
                FILE_NAME                 = P_FNAME
                DATA_SHEET_NAME           = V_SHEET_NAME
           TABLES
                DATA_TAB                  = TLX
           EXCEPTIONS
                FILE_NOT_EXIST            = 1
                FILENAME_EXPECTED         = 2
                COMMUNICATION_ERROR       = 3
                OLE_OBJECT_METHOD_ERROR   = 4
                OLE_OBJECT_PROPERTY_ERROR = 5
                INVALID_FILENAME          = 6
                INVALID_PIVOT_FIELDS      = 7
                DOWNLOAD_PROBLEM          = 8
                OTHERS                    = 9.
      IF SY-SUBRC NE 0.
        WRITE:/ 'ERROR OPENING EXCEL'.
      ENDIF.
    ELSE.
      WRITE:/ 'ERROR OR NO DATA'.
    ENDIF.

  • How to invoke COM DLL from Forte

    Is there a sample available for C wrapper for COM Methods ?

    Talking to a COM object from Forte is possible if the COM object uses apartment model threading. Anything else and you will have problems.
    Refer to the "Integrating with windows and macintosh" manual and the chapter on OLE integration. COM is just OLE with extras. DCOM is just COM/OLE with remote support. Microsoft likes to put fancy names on old tech.
    You will need to use the olegen program supplied with forte to generate a forte supplier plan that wraps the COM object. Then you can use the forte objects just like a COM object.
    Be aware though that COM has a number of limitations that you must be carefull of. You MUST talk to the COM object using the same thread that you created the COM object in. Don't initialise in the Init method and then call it from somewhere else (Service object Init methods are run from a different thread).
    It is useally safest to single thread all access to the object.

  • Re: I : Workflow applications -Reply

    Daniela,
    We at Claremont Technology Group are in the implementation stage of a
    Forte/Workflow system for Public Employee Retirement systems. We are using
    Action Technologies' "Action Workflow" to handle the workflow portion of the
    application. Action has an API set that allows you to build a custom workflow
    system with any development tool. Integration with Forte is fairly complex as
    all API's need to be wrappered. Action is very expensive, and their technical
    support staff has not been real helpful to date, as they aren't familiar with
    Forte. If you have any questions, feel free to email me.
    To: forte-users @ Sagesoln.com (forte user group) @ Internet
    cc: (bcc: Michael George/Central Region/Claremont)
    From: Daniela.Chiaberto @ CSI.IT (Chiaberto Daniela) @ Internet @ WORLDCOM
    Date: 09/18/96 09:09:37 AM CDT
    Subject: I : Workflow applications -Reply
    I forward this reply to the list because I think it can be of general
    interest.
    Dear Forte users,
    we have to develop applications based on workflow concepts, having to to
    manage the flow of administrative documents in the Public Administration
    world.
    Has anyone had any experiences of developing such applications using Forte
    technology (by itself or integrated with some workflow or groupware
    specific products)?
    Do you have any ideas?
    Any suggestions would be very appreciated.
    Thanks
    Daniela
    >>--------
    Chiaberto Daniela
    CSI-PIEMONTE
    Cso Unione Sovietica 216
    10134 Torino ITALY
    tel: +39 11 4618332
    fax: +39 11 4618471
    e-mail: [email protected]
    Hi, Daniela
    This spring I evaluated and tested more than 20 the most
    wide-spread workflow packages. The idea was not to develop
    this part of our Forte Application by ourselves, but try to
    incorporate into it COTS software. The only package that
    was very close to be incorporated (through using OLEGEN),
    and I was able to create classes in Forte and run very simple
    application, was ViewStar.
    Unfortunately, the real implementation of workflow part in our
    system was postponed till the next phase, so we just keep
    this in mind. And ViewStar costs a lot of money.
    If You need details, please, drop a e-mail.
    Pavel
    Pavel Ryzhkov
    Price Waterhouse LLP
    BDM Integration Team
    [email protected]

    Hi
    You should turn the unit upside down and should wait until the unit dried.
    In best case the unit should power up properly but it could be possible that your motherboard or another part like RAM module or keyboard could be affected.
    Something similar happened to my girlfriends notebook. In my case the RAM module was dead and notebook could not boot up I replaced the RAM and was happy to see the Toshiba splash screen

  • RE: OLE

    I have trying to integrate MSGraph in Forte for a while with
    little success. I agree with you that Forte example is too
    basic.
    Perhaps your problem is simpler but I found impossible to
    send data from Forte to the OLE Object. I've been said
    that it's easier through Excel.
    When you generate project Graph from Olegen, you start with
    a broken hierarchy that needs to be rebuilt.
    A posting from Pavel Ryzhkov on 14/10/97 may be helpful for
    you. If you cannot access it, I can send you a copy.
    Regards,
    Jesus Zamarreno
    EAM Sistemas Inform&aacute;ticos S.L.
    C/ Padre Llanos, 33 47014 Valladolid
    Tlf.: (983) 352922 Fax: (983) 352115
    e-mail: [email protected]
    De: Jean Baptiste BRIAUD <[email protected]>
    A: [email protected]
    Asunto: OLE
    Fecha: viernes 31 de octubre de 1997 17:44
    Hi,
    I need to use MSGraph with OLE integration.
    I saw Forte example, but it seem too basic :
    How to know what to do with all this classes in
    the imported project Graph ?
    How to know which CDispatch's attribute
    to call ?
    I didn't found any doc on Office, Microsoft Shared, ..
    directory.
    Thanks in advance,
    Jean-Baptiste BRIAUD, [email protected]
    SEMA GROUP
    16 rue Barbes
    92126 Montrouge
    France

    DDE is an interface much like OLE - e.g. it has calls to invoke methods and set properties - again you need the doc from the vendor to know what properties to set and methods to call. Likewise the C interface can be used to call public apis exposed by the vendor in a DLL or EXE. This uses the ORA_FFI package. Again the interface is simple (fo someone who understands C) but without the vendor doc about any APIs they expose it's of no use.
    What interfaces does the software expose?

  • Interfacing to Microsoft outlook

    Is there some way to call MicroSoft Outlook from TOOL Code? We would like
    to be able to send a list of
    text files on disk as mail messages using Outlook from within TOOL.
    Thanks in advance for any help.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    I'm including a OLE2 integration with Outlook I did about a year ago.
    The platform was NT 4.0 and Outlook from Office 97. It sends mail with
    an attachment. I just tested it with Forte 3.J.1 and it works.
    You need to run olegen to create the Forte Outlook pex file.
    Good luck,
    Gabriel J. Choza
    Forte Technical Sales
    [email protected]
    http://www.forte.com
    From: Michael Strauss <[email protected]>
    To: "'Jones, Kerreck'" <[email protected]>,
    "'[email protected]'" <[email protected]>
    Subject: RE: interfacing to Microsoft outlook
    Date: Wed, 18 Nov 1998 09:52:10 +1100
    X-Mailer: Internet Mail Service (5.5.2232.9)
    Sender: [email protected]
    Reply-To: Michael Strauss <[email protected]>
    Mazda Australia takes every precaution to ensure email messages are virusfree.
    >
    There are two ways that I know of to interface Fort&eacute; with Outlook (and MS
    mail generally). You can either use ActiveX as the method of communication
    or C wrappering to call the MS mail dll. Outlook is mapi compliant, that is
    it supports the mapi API.
    We have successfully integrated mapi using C wrappering but have had only
    moderate success with ActiveX. The problem with ActiveX has been with
    registering the component on the client machines. If you or anyone else has
    done this successfully, I would really like to hear how it was done.
    Michael Strauss
    Mazda Australia Pty Limited
    -----Original Message-----
    From: Jones, Kerreck [mailto:[email protected]]
    Sent: Wednesday, 18 November 1998 3:07
    To: '[email protected]'
    Subject: interfacing to Microsoft outlook
    Is there some way to call MicroSoft Outlook from TOOL Code?
    We would like
    to be able to send a list of
    text files on disk as mail messages using Outlook from
    within TOOL.
    Thanks in advance for any help.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:http://pinehurst.sageit.com/listarchive/>
    This message has successfully passed virus checking.
    Mazda Australia takes every precaution to ensure email messages are virusfree. For complete protection, you should virus test this message.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • Integrating True DBGrid 6.0 with Forte using OLEAutomation

    I'm attempting to manipulate an Appex TrueDBGrid object using Forte TOOL
    code. So far I've made it through the following steps:
    Used olegen to create a PEX file for the TrueDBGrid60 ocx file (tdbg6.ocx).
    Imported this pex file into my workspace.
    Created a display project with TrueDBGrid60, Framework, DisplayProject and
    OLE as supplier plans
    Added a window class
    On Window, added an OLE Field with mapped type ITrueDBGridCtrl.
    I attempted to interpret the following VB code for adding a column:
    ' Create a new Column 0
    Dim C As TrueDBGrid60.Column
    Set C = TDBGrid1.Columns.Add(0)
    ' Initialize the new Column 0
    With C
    .Visible = True ' Make it visible
    .DataField = "LAST" ' Set the column's database field
    .Caption = "Last Name" ' Set the column's caption
    End With
    ' Make Column 0 as wide as Column 1
    C.Width = TDBGrid1.Columns(1).Width
    I can get this code to work in VBA, but I have difficulty when converting in
    to Forte Tool code.
    I added the following code to the Window class init method:
    super.Init();
    dbgrid = new();
    dbgrid.objectReference; -- not sure what to set this to?
    col : TrueDBGrid60.Column;
    cols : TrueDBGrid60.Columns = new();
    cols.add(0); -- this line causes run time error because object reference is
    not set.
    //dbgrid.columns = cols;
    //dbgrid.classicAdd(cols); these lines don't work
    col.visible = true;
    col.caption = 'Column 1';
    col.width = 1.5;
    This is as far as I've gone.
    Has any one used the Appex TrueDBGrid within a Forte Window?
    If yes, Is there any documentation on this subject that clarify the
    necessary processes?
    Thanks
    Brian
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi Mastek,
    You should be able to accomodate your needs with respect to integration of your AD accounts with SAP ECC ABAP. This can be done via LDAP connector configuration. The below has info on how to perfrom the configuration at a high level. You will have to integrate, and map certain user data. You may also want to do some LDAP Connector research:
    [http://help.sap.com/saphelp_nw70/helpdata/en/10/1a063a15c611d4b61f0000e835363f/content.htm]
    On the Java stack - you can also confugure UME to integrate/authenticate with AD:
    [http://help.sap.com/saphelp_nw70ehp2/helpdata/en/12/7678123c96814bada2c8632d825443/content.htm]
    Hope this helps!

Maybe you are looking for