Requires Free Membership to View
When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.
Hannah Smalltree, Editorial Director
Before:
/*@(#)BAPIRET2 %I% SAP %E% */
/*
* BAPIRET2
*
*
* File generated from SAP Data Dict
* Fri Jan 10 16:59:09 2003
*
*/
#ifndef BAPIRET2_H
#define BAPIRET2_H
typedef struct BAPIRET2
{
SAP_CHAR Type [1];
#define BAPIRET2_TYPE_LN 1
#define BAPIRET2_TYPE_TYP RFCTYPE_CHAR
.
.
.After:
/*@(#)BAPIRET2 $Id$ SAP */ /* * BAPIRET2 * * * File generated from SAP Data Dict * SAP system:.. DV4 * SAP release:. 46C * Date:........ Fri May 02 09:17:53 2003 * * * # Of fields:.................. 14 * Size in 1 byte per SAP_UC:... 548 * Size in 2 bytes per SAP_UC:... 1088 * Size in 4 bytes per SAP_UC:... 2172 * */ /*!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! This file has been generated against a system ! ! that is not UNICODE ready. ! ! ! ! This file may be used for RFC programs: ! ! ! ! - that are not-UNICODE enabled and link to ! ! librfc.a, librfccm.sl or librfc32.lib ! ! ! ! In this case the resulting programs can ! ! be used to communicate with systems that use ! ! compatible structures. (No changes where ! ! applied to the structure, or fields where ! ! added at the end of the structure). ! ! ! ! The partner system may be a UNICODE or a ! ! non-UNICODE systems. ! ! ! ! - that are UNICODE enabled and link to either ! ! librfcu.a librfcum.sl or librfc32u.dll ! ! ! ! In this case the resulting programs can only ! ! be used to communicate with non-UNICODE ! ! systems. ! ! ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! You *MUST* regenerate this file and recompile ! ! this programs in order to communicate with ! ! UNICODE systems ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ! ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! */ . . .
I have no clue why installing the .NET Framework upsets DCOM Connector, but I can strongly recommend that you switch over to SAP's .NET Connector (available from http://service.sap.com/connectors). This product is fully integrated with Visual Studio .NET and does not have any of the "limitations" of the DCOM Connector. There is no porting tool available from SAP, so you will have to slightly modify your existing source code, but - provided that you have used proper componentization in your existing software - this should not be too hard. My own experiences with the new product are almost totally positive. If you find the official SAP documentation insufficient, I can recommend my forthcoming article on the product, most likely published in the July/August 2003 issue of the SAP Professional Journal (http://www.sappro.com).
This was first published in June 2003
Join the conversationComment
Share
Comments
Results
Contribute to the conversation