Variants in forte

Can anyone help me?
I am trying to use a Crystal OCX to create reports. I do not want to
view the report I want to send it directly to the printer. I believe I
have located how the code needs to read but, crystal expects a variant
and I am unable to locate how to create a variant.
Example of the code:
CrystalReport1.Destination = 1;
The 1 is the variant.
Travis Theel
Olsten Health Services
[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Similar Messages

RE: Variants in forte [Ref:C614383] [Ref:C635762]

Hi Travis.
Another quick way of creating a variant would be
CrystalReport1.Destination = VariantInteger(Value = 1);
The Integrating With Windows and Macintosh manual has information on using
variants, but it isn't the clearest subject in the documentation. I've obtained
a few technotes from Forte support (in regards to integrating with Word and
Excel, but the principle is the same), and I found these to be helpful as well.
Good luck.
Steve Elvin
Systems Developer
Frontline Ltd.
UK.
-----Original Message-----
From: INTERNET [email protected]
Sent: Monday, August 17, 1998 5:41 PM
To: Steve Elvin; X400
p=NET;a=CWMAIL;c=GB;DDA:RFC-822=forte-users(a)sagesoln.com;
Cc: X400 p=NET;a=CWMAIL;c=GB;DDA:RFC-822=JCBock(a)olstenhs.com;; X400
p=NET;a=CWMAIL;c=GB;DDA:RFC-822=MKennedy(a)olstenhs.com;
Subject: Variants in forte [Ref:C614383]
Can anyone help me?
I am trying to use a Crystal OCX to create reports. I do not want to
view the report I want to send it directly to the printer. I believe I
have located how the code needs to read but, crystal expects a variant
and I am unable to locate how to create a variant.
Example of the code:
CrystalReport1.Destination = 1;
The 1 is the variant.
Travis Theel
Olsten Health Services
[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
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 Travis.
Another quick way of creating a variant would be
CrystalReport1.Destination = VariantInteger(Value = 1);
The Integrating With Windows and Macintosh manual has information on using
variants, but it isn't the clearest subject in the documentation. I've obtained
a few technotes from Forte support (in regards to integrating with Word and
Excel, but the principle is the same), and I found these to be helpful as well.
Good luck.
Steve Elvin
Systems Developer
Frontline Ltd.
UK.
-----Original Message-----
From: INTERNET [email protected]
Sent: Monday, August 17, 1998 5:41 PM
To: Steve Elvin; X400
p=NET;a=CWMAIL;c=GB;DDA:RFC-822=forte-users(a)sagesoln.com;
Cc: X400 p=NET;a=CWMAIL;c=GB;DDA:RFC-822=JCBock(a)olstenhs.com;; X400
p=NET;a=CWMAIL;c=GB;DDA:RFC-822=MKennedy(a)olstenhs.com;
Subject: Variants in forte [Ref:C614383]
Can anyone help me?
I am trying to use a Crystal OCX to create reports. I do not want to
view the report I want to send it directly to the printer. I believe I
have located how the code needs to read but, crystal expects a variant
and I am unable to locate how to create a variant.
Example of the code:
CrystalReport1.Destination = 1;
The 1 is the variant.
Travis Theel
Olsten Health Services
[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

RE: Variants in forte

To create a variant, you need to instantiate a variant object and set
its value. Forte supports many variant classes mapping to their OLE
variant types, and VariantInteger is one of those. You can try the
following:
myVInt : VariantInteger = new;
myVInt.Value = 1;
CrystalReport1.Destination = myVint
Hope this helps.
Lenny Hon
Descartes Systems Group
-----Original Message-----
From: Travis Theel [SMTP:[email protected]]
Sent: Monday, August 17, 1998 11:49 AM
To: '[email protected]'
Cc: Chris Bock; Mike Kennedy
Subject: Variants in forte
Can anyone help me?
I am trying to use a Crystal OCX to create reports. I do not want to
view the report I want to send it directly to the printer. I believe
I
have located how the code needs to read but, crystal expects a variant
and I am unable to locate how to create a variant.
Example of the code:
CrystalReport1.Destination = 1;
The 1 is the variant.
Travis Theel
Olsten Health Services
[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

In the 2E release there is a Sleep method on OperatingSystem, it
should be documented in the 2.0 addendum doc. This will put
the entire process to sleep for a specified number of milliseconds.
-jak
Jak Mang
Forte Software

RE: (forte-users) returning variants from OLE methodcalls

I'm getting an error when calling an OLE method which
requires two VARIANT
parameters, one input and one output. Both parameters are treated as
arrays
by the OLE method.
Error during Invoke; status code: -2147352562(0x8002000E)This error is "Invalid Number of Parameters"
The code itself, I cannot really comment on as I have had very little
experience with COM objects
Cheers
David McPaul
Lumley Technology
This message has been Content Filtered by MailMarshal.
---------------------------------------------------------------------

As an FYI, to find out what the error message means, you can take the hex
number (in this case 0x8002000E) and search through the winerror.h file.
That will give you a better idea of what the actual problem is.
Katie Tierney
Akili Systems Group
601 Jefferson, Suite 3975
Houston, Texas 77002
Office: (713) 655-1400
Cell: (409) 255-1643
"The bitterness of poor quality remains long after the sweetness of low
price is forgotten" --Larry Anderson
-----Original Message-----
From: David McPaul [mailto:dmcpaullumley.com.au]
Sent: Tuesday, March 07, 2000 5:27 PM
To: 'Isaak Peretsman'; forte-userslists.xpedior.com
Subject: RE: (forte-users) returning variants from OLE method calls
I'm getting an error when calling an OLE method which
requires two VARIANT
parameters, one input and one output. Both parameters are treated as
arrays
by the OLE method.
Error during Invoke; status code: -2147352562(0x8002000E)This error is "Invalid Number of Parameters"
The code itself, I cannot really comment on as I have had very little
experience with COM objects
Cheers
David McPaul
Lumley Technology
This message has been Content Filtered by MailMarshal.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Conversion of 1.2 JATO project (non-Forte IDE) to S1AF (JATO) 2.0

JATO Team,
First of all, thank you very much for the Studio integration. It
looks very promising in terms of development time consumption,
deployment to S1AS7, etc., etc. It is impossible to observe all
advantages for so short period of time.
The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio 4,
update 1 (EE) with JDK 1.4 along with the Sun One Application Server
7 (W2000). Everything looks okay, at least all basic tasks listed in
the "Getting Started" manual (project/view/model creation, basic db
connection, running of a test application with the usage of the
Studio's default Tomcat container, etc.) work proper.
During the installation of S1AF module on the top of the Sun ONE
Studio 4, update 1 (EE) I've got an invitation to convert the
existing project to the new environment. As I realized the only JATO
project integrated/created with Forte IDE is applicable for this auto-
conversion (please correct me, if I am wrong. It could solve a lot of
my problems).
Since we are using JBuilder5 IDE and our JATO 1.2 project is
integrated with this IDE I manually re-created project in the Studio
with its file structure, adjusted the project web.xml file, etc. This
new project looks like a proper one (Studio recognize all methods,
fields, bean patterns, e.g.) except at least one "small" thing. All
java files (project viewBeans, Models, custom viewBeanHelpers a.k.a.
pure java) came up with the same wizard image:java class. Stutio with
the S1AF module reserves the special images (and appropriate studio
properties, of course!) for View and Model. Namely this allows to see
the following structure for a ViewBean, for example, in the Studio:
Modules
ProjectName.ModuleName
FooViewBean
JavaSource
JSPs
Non-Visual Components
View Components
On the other hand, I could add either new View or Model in my
manually converted project and add any View Component or bind the
Model fields, for example. Also, the ProjectModuleServlet has been
converted proper. I tried to convert each View/Model class inside the
Studio to its proper wizard image and failed. Addition of a View
Components (with an appropriate code fragments) via the Studio or
auto-binding of model fields is an essential part of 2.0 and should
drastically speed up the development process as it is designed.
Questions:
1. What I missed in my manual conversion of 1.2 JATO project to the
SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
compatible classes (Views and Models) to be recognizable by Studio
wizard (JATO 2.0)?
To be more specific. Some deltas between JATO 1.2 and JATO 2.0 are as
follows (related to a ViewBean):
====++++++++++++++======
JATO 1.2 viewBean extension upon creation:
public class FooViewBeanViewBean extends ViewBeanBase
implements ViewBean
========================
JATO 2.0 (S1AF) version: viewBean extension upon creation:
public class FooViewBean extends BasicBeanBase
====++++++++++++++======
JATO 1.2 viewBean createChild(...) method for one static looks
like:
protected View createChild(String name)
if (name.equals(CHILD_STATICTEXT1))
StaticTextField child = new StaticTextField
(this,
getDefaultModel(),
CHILD_STATICTEXT1,
CHILD_STATICTEXT1,
CHILD_STATICTEXT1_RESET_VALUE,
null);
return child;
========================
JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed (as
a least) to createChildReserved(...):
protected View createChildReserved(String name) {
if (name.equals(CHILD_STATICTEXT1)) {
com.iplanet.jato.view.BasicDisplayField child =
new com.iplanet.jato.view.BasicDisplayField(this,
STATICTEXT1);
return child;
====++++++++++++++======
JATO 1.2 viewBean registerChildren() method for the basic field
types looks like:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1, StaticTextField.class);
registerChild(CHILD_TEXTFIELD1, TextField.class);
registerChild(CHILD_BUTTON1, Button.class);
========================
JATO 2.0 (S1AF) version: viewBean registerChildren() method:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_TEXTFIELD1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_BUTTON1,
com.iplanet.jato.view.BasicCommandField.class);
Is it correct to say that all existing custom Views/Models
(compatible with JATO 1.2) should be converted to their JATO 2.0
variants to be visible by the Studio?
On the other hand, fast overview of 2.0 API shows that the JATO 1.2
is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
example). What exactly (only deprecated methods?) should be adjusted
in the project code (1.2), if necessary, to be visible by Studio as a
View or Model component?
2. Where it is possible to find the list of deprecated methods (from
JATO 1.2 to JATO 2.0 versions). It is difficult sometimes to compare
two versions of API docs (1.2 and 2.0) or compare logs between
versions. Also, JATO 2.0 is significantly larger than 1.2 version. If
the later obviously inherits the ND conversion stage (via the
previous versions), the former obviously has additions incoming from
the integration with the Studio (a.k.a. Forte 4.0).
3. What is the current/future Sun/JATO Team policy with regards to
JATO source code access (version 2.0, at least)? The reason of this
question is as follows: in order to display dates formatted on the
screens we adjusted a couple of JATO 1.2 core classes, for example.
The only minimal, absolutely necessary changes in JATO 1.2 was made,
but anyway...
Sorry for so long multiple question. As Todd wrote in his
announcement mail: "We think you will be very pleased with the new
product...". This is exciting moment, I believe, for JATO Team as
well as for any team involved into the conversion of the full size
application/product from ND to J2EE realm with the JATO as
an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally). The
last step is left in this spiral process to enjoy the ND_Studio
attractive features in the open source environment.
Thank you very much in advance.
Vladimir Ivanov

I'll get some file templates ASAP and provide them to the group.
As for source code, I'm not sure what the policy is. JATO 1.2 is very
close to what JATO 2.0 is, so that should suffice for now.
The community will be informed when we know more about source availibility.
craig
vivanov4114 wrote:
Craig,
Thank you for the answer. To be honest with you I tried to do exactly
the same: I created the small test project and made an attempt to
adjust the existing *.xml files to the new ones. I got some results,
otherwise I couldn't even see my original 1.2 project in the Studio.
Since I am a newcomer in the Studio, I definitely missed something in
my adjustments. I'll try to observe my changes with the fresh head.
On the other hand, I am afraid that my samples are very pure. If you
could post or send me examples of jatoapp.xml and web.xml files (say
for any of you test project) or excerptions from them with the
appropriate patterns (ViewBean and Model peers, at least), I would be
very appreciated. My mail is: vivanov@b...
In the worst-case scenario I see the workaround: to re-create the
project for one of our releases with the Forte 4.1 IDE and auto-
convert it into the JATO 2.0/Studio world using the Studio
facilities. We must get the current project fully
integrated/converted with/to the Studio (at certain point) because,
first, we expect massive coding with the GUI components involved soon
and, secondly, we have around thousand classes related to JATO only
(and a lot of extras).
Coming back to the question #3 from this post. Now we have full
access to the version 1.2, not only to the JATO 1.2 jar file(I
explained some reasons below). Would we expect the same Sun/JATO Team
policy with JATO 2.0?
Thank you again,
Vlad
--- In SunONE-JATO@y..., "cvconover" <craig.conover@s...> wrote:
It doesn't appear that anyone has responded to this so I am goingto
give you the short answer:
The reason you don't see your ViewBeans and Models showing up with
there "wizard created" icons is because of just that. They weren't
created via the wizards. The wizards create xml formatted filesthat
contain metadata of how/what to generate for the ViewBeans and
Models.
ViewBeans will have a .viewbean fiel, Models will have a .sqlmodel
file (for SQL Models), etc. The content of these files describesthe
code that needs to be generated in the corresponding Java classfile.
So LoginViewBean.java will have a peer LoginViewBean.viewbean file.
The code that is generated is place in protected code blocks thatcan
not be modified in the Studio and should not be modified outsidethe
Studio because the code will likely be regenerated and custom mods
inside the protected blocks will be lost.
Now you can make a JATO 1.2 app appear in the Studio just like aJATO
2.0 app by adding a jatoapp.xml file with the proper content and
adjusting your web.xml properly, but it's much more work to getyour
v1.2 ViewBeans and Models to show up like wizard created versions.
Furthermore, even more work to get the display fields to show up
visually.
The good news is that v1.2 ViewBeans will work with newly wizard
created ViewBeans. And if you do go through the trouble of making
your ViewBeans Studio visible like your wizard created ViewBeans,
adding new display fields visually will work along side yourmanually
created fields.
Try creating a new JATO app using the Studio wizards and then go to
the Filesystems tab and look for the jatoapp.xml file and theweb.xml
file.
I am looking for an email that I have that explains how to do a
partial, manual upgrade.
Also, you will get rid of your JATO 1.2 jar and replace with theJATO
2.0 jar in your lib dir.
Hope this will suffice for now.
craig
--- In SunONE-JATO@y..., "vivanov4114" <vivanov@b...> wrote:
JATO Team,
First of all, thank you very much for the Studio integration. It
looks very promising in terms of development time consumption,
deployment to S1AS7, etc., etc. It is impossible to observe all
advantages for so short period of time.
The SOAF (JATO) 2.0 is installed on the top of the Sun ONE Studio4,
update 1 (EE) with JDK 1.4 along with the Sun One ApplicationServer
7 (W2000). Everything looks okay, at least all basic tasks listedin
the "Getting Started" manual (project/view/model creation, basic
db
connection, running of a test application with the usage of the
Studio's default Tomcat container, etc.) work proper.
During the installation of S1AF module on the top of the Sun ONE
Studio 4, update 1 (EE) I've got an invitation to convert the
existing project to the new environment. As I realized the onlyJATO
project integrated/created with Forte IDE is applicable for thisauto-
conversion (please correct me, if I am wrong. It could solve a
lot
of
my problems).
Since we are using JBuilder5 IDE and our JATO 1.2 project is
integrated with this IDE I manually re-created project in theStudio
with its file structure, adjusted the project web.xml file, etc.This
new project looks like a proper one (Studio recognize all
methods,
fields, bean patterns, e.g.) except at least one "small" thing.All
java files (project viewBeans, Models, custom viewBeanHelpersa.k.a.
pure java) came up with the same wizard image:java class. Stutiowith
the S1AF module reserves the special images (and appropriate
studio
properties, of course!) for View and Model. Namely this allows tosee
the following structure for a ViewBean, for example, in the
Studio:
Modules
ProjectName.ModuleName
FooViewBean
JavaSource
JSPs
Non-Visual Components
View Components
On the other hand, I could add either new View or Model in my
manually converted project and add any View Component or bind the
Model fields, for example. Also, the ProjectModuleServlet hasbeen
converted proper. I tried to convert each View/Model class insidethe
Studio to its proper wizard image and failed. Addition of a View
Components (with an appropriate code fragments) via the Studio or
auto-binding of model fields is an essential part of 2.0 and
should
drastically speed up the development process as it is designed.
Questions:
1. What I missed in my manual conversion of 1.2 JATO project tothe
SOAF (JATO) 2.0 realm? What should I correct in my JATO 1.2
compatible classes (Views and Models) to be recognizable byStudio
wizard (JATO 2.0)?
To be more specific. Some deltas between JATO 1.2 and JATO 2.0are
as
follows (related to a ViewBean):
====++++++++++++++======
JATO 1.2 viewBean extension upon creation:
public class FooViewBeanViewBean extends ViewBeanBase
implements ViewBean
========================
JATO 2.0 (S1AF) version: viewBean extension upon creation:
public class FooViewBean extends BasicBeanBase
====++++++++++++++======
JATO 1.2 viewBean createChild(...) method for one static looks
like:
protected View createChild(String name)
if (name.equals(CHILD_STATICTEXT1))
StaticTextField child = new StaticTextField
(this,
getDefaultModel(),
CHILD_STATICTEXT1,
CHILD_STATICTEXT1,
CHILD_STATICTEXT1_RESET_VALUE,
null);
return child;
========================
JATO 2.0 (S1AF) version: viewBean createChild(...) is renamed(as
a least) to createChildReserved(...):
protected View createChildReserved(String name) {
if (name.equals(CHILD_STATICTEXT1)) {
com.iplanet.jato.view.BasicDisplayField child =
new com.iplanet.jato.view.BasicDisplayField(this,
STATICTEXT1);
return child;
====++++++++++++++======
JATO 1.2 viewBean registerChildren() method for the basic field
types looks like:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
StaticTextField.class);
registerChild(CHILD_TEXTFIELD1, TextField.class);
registerChild(CHILD_BUTTON1, Button.class);
========================
JATO 2.0 (S1AF) version: viewBean registerChildren() method:
private void registerChildren() {
registerChild(CHILD_STATICTEXT1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_TEXTFIELD1,
com.iplanet.jato.view.BasicDisplayField.class);
registerChild(CHILD_BUTTON1,
com.iplanet.jato.view.BasicCommandField.class);
Is it correct to say that all existing custom Views/Models
(compatible with JATO 1.2) should be converted to their JATO 2.0
variants to be visible by the Studio?
On the other hand, fast overview of 2.0 API shows that the JATO1.2
is a sub-set of the 2.0 (BasicViewBean extends ViewBeanBase, for
example). What exactly (only deprecated methods?) should beadjusted
in the project code (1.2), if necessary, to be visible by Studio
as
a
View or Model component?
2. Where it is possible to find the list of deprecated methods(from
JATO 1.2 to JATO 2.0 versions). It is difficult sometimes tocompare
two versions of API docs (1.2 and 2.0) or compare logs between
versions. Also, JATO 2.0 is significantly larger than 1.2
version.
If
the later obviously inherits the ND conversion stage (via the
previous versions), the former obviously has additions incomingfrom
the integration with the Studio (a.k.a. Forte 4.0).
3. What is the current/future Sun/JATO Team policy with regards
to
JATO source code access (version 2.0, at least)? The reason ofthis
question is as follows: in order to display dates formatted onthe
screens we adjusted a couple of JATO 1.2 core classes, forexample.
The only minimal, absolutely necessary changes in JATO 1.2 wasmade,
but anyway...
Sorry for so long multiple question. As Todd wrote in his
announcement mail: "We think you will be very pleased with the
new
product...". This is exciting moment, I believe, for JATO Team as
well as for any team involved into the conversion of the fullsize
application/product from ND to J2EE realm with the JATO as
an application framework (1.0, 1.1.x, 1.2.X, and 2.0 finally).The
last step is left in this spiral process to enjoy the ND_Studio
attractive features in the open source environment.
Thank you very much in advance.
Vladimir IvanovTo download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
[Non-text portions of this message have been removed]

Re: (forte-users) Ok, what's the "secret" for setting serverside envi

Dear Robinson,
It seems to be that you have 2 ways of solving the problem:
1) restart forte after setting the environment variables
2) write a little application which sets the required variables, using
the task.part.OperatingSystem.SetEnv(name,value) method.
If you have to chage the variables rarely, then it`s easier to restart forte,
otherwise I would suggest to use the SetEnv function...
Best Regards,
Tamas Deak
"Robinson, Richard" wrote:
Subject says it all.
We have a bunch of environment variables that are used by the server side
objects. What I want to do is change the value of some of the variables
prior to running my application in Forte Development IDE (3.0.G.2). I've
tried to set the environment variables via NT's registry, but it appears
that at execution time the variables take on the value of whatever they are
for the node manager.
Most IDE's I've worked with before have a way to specify environment
variables right in the tool. Forte doesn't appear to have that capability -
say it ain't so!
Any clues?
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]
Tamas Deak
Lufthansa Systems Hungary
(forte developer)
2-6 Mazsa ter, Budapest, 1107, HUNGARY
(36-1) 4312 973
[email protected]
[email protected][email protected]-

Richard,
There is no way of changing the environment variable once the Node
Manager is up. You will have to shutdown the node manager and then restart
it to have the new environment variables take effect. Sorry, there is no
secret way of doing this that I know of.
But you can set the variables on you development machine and run you
application without distributing. This way the partition will be running in
your client machine and not the server.
Another way we have also got around this is by having a special
environment variable on the client side that opens a admin screen when you
run you application. This admin screen will allow you to change the
environment variables and then set them on the server partition. You will
have to do come coding on the server to make this happen but if you are
using a framework then it should be easy. We call this developer reconnect
facility. It only can be activated by the special client side environment
variable. I comes in very handy when we are development and want to change
the database on the server partition.
Hope this help.
ka
Kamran Amin
Framework, Inc.
303 South Broadway
Tarrytown, NY 10591
(914) 631-2322x121
[email protected]
http://www.frameworkinc.com/
-----Original Message-----
From: Robinson, Richard [mailto:[email protected]]
Sent: Thursday, November 04, 1999 7:23 AM
To: [email protected]
Subject: (forte-users) Ok, what's the "secret" for setting server side
environment varia bles when running in the Forte Development
Environment?
Subject says it all.
We have a bunch of environment variables that are used by the server side
objects. What I want to do is change the value of some of the variables
prior to running my application in Forte Development IDE (3.0.G.2). I've
tried to set the environment variables via NT's registry, but it appears
that at execution time the variables take on the value of whatever they are
for the node manager.
Most IDE's I've worked with before have a way to specify environment
variables right in the tool. Forte doesn't appear to have that capability -
say it ain't so!
Any clues?
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

Re: (forte-users) C++ version compatibility question. Fortev30L2 on D

Dirk:
I ran into a similar problem. I added an other flag to my fcompile script and
it seems to be working fine, your mileage may vary. The flag was
-cflags "-oldcxx only"
Dwayne Kryger
"Haben, Dirk" <[email protected]> on 08/25/99 02:09:16 AM
To: "'Soapbox Forte Users'" <[email protected]>
cc: (bcc: Dwayne Kryger/SEH)
Subject: (forte-users) C++ version compatibility question. Forte v30L2 on
Digital Unix 4 d and C++ version ???
G'day Folxs
Just installed Forte as a Simple Server on a Digital UNIX (v4.0d) box (being
a VMSbot it was much easier than I thought). We want to use it to interface
with an existing web client. The Forte part is to provide us a scalable
access path to Oracle DBs on the VMS machine; already running Forte.
I'm having trouble finding media that contains C++ v5.4.-006 for the Unix
box. Does anyone know of/has used higher versions of C++ without too much
drama? How about v5.7 or even v6.1? We will be using extensive C++
interfacing to existing web pages!
NB: The current web system client is compiled using EGCS 2.91.66.
TIA,
/[:-)irK
Dirk Haben, Perth WA
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

Dirk:
I ran into a similar problem. I added an other flag to my fcompile script and
it seems to be working fine, your mileage may vary. The flag was
-cflags "-oldcxx only"
Dwayne Kryger
"Haben, Dirk" <[email protected]> on 08/25/99 02:09:16 AM
To: "'Soapbox Forte Users'" <[email protected]>
cc: (bcc: Dwayne Kryger/SEH)
Subject: (forte-users) C++ version compatibility question. Forte v30L2 on
Digital Unix 4 d and C++ version ???
G'day Folxs
Just installed Forte as a Simple Server on a Digital UNIX (v4.0d) box (being
a VMSbot it was much easier than I thought). We want to use it to interface
with an existing web client. The Forte part is to provide us a scalable
access path to Oracle DBs on the VMS machine; already running Forte.
I'm having trouble finding media that contains C++ v5.4.-006 for the Unix
box. Does anyone know of/has used higher versions of C++ without too much
drama? How about v5.7 or even v6.1? We will be using extensive C++
interfacing to existing web pages!
NB: The current web system client is compiled using EGCS 2.91.66.
TIA,
/[:-)irK
Dirk Haben, Perth WA
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

ActiveX in Forte v3

Hello,
I'm trying to manage a financial printer using an activex control to
access it.
My problem is passing the VersionRequired variant attribute, I dont know
exactly the type object to pass to this attribute.
Using a VariantDispatcher type, Forte execute a exception saying that the
object isn't set as OLE object.
Using another variant type, ocurr a exception saying that the CDispatcher
are not code.
How can I to do it?
Tank and excuse me by my little english.
Jose Antonio Zapata Rey
[email protected]

Hello,
I'm trying to manage a financial printer using an activex control to
access it.
My problem is passing the VersionRequired variant attribute, I dont know
exactly the type object to pass to this attribute.
Using a VariantDispatcher type, Forte execute a exception saying that the
object isn't set as OLE object.
Using another variant type, ocurr a exception saying that the CDispatcher
are not code.
How can I to do it?
Tank and excuse me by my little english.
Jose Antonio Zapata Rey
[email protected]

Forte NodeMgr...

Forte Users,
I was using Forte when my disk crashed ( someone steped on the
cable!) , but after that ( rebooting the machine to re-mount the disk ), I
just cant get the NodeMgr running. It always times out the attempt to
connect to the repository.
Fast help is appreciated!
Thanks,
C. M. Motta

This may help -worth a try
- make sure the node manager process is truly "dead" by issuing the kill
command if it isn't
- make sure the repository process is truly "dead" and not running by
issuing the kill command if it is still "up"
- make sure you have no ftexec processes running for this
nodemanager/repository
- make sure your environment settings are set
(like setenv FORTE_REPOSNAME CentralRepository
setenv FORTE_ENVNAME CentralEnv, etc.)
- now issue the start_nodemgr -e <node manager name> command
- issue the start_repos -fr ob:central -n CentralRepository (the names
will vary for your repos names)
May or may not help or you may have already tried it - worth a shot.
Regards,
Peggy Adrian Eli Lilly & Co. [email protected]

Layout variant not working

Hi ,
I have executed a report . I hide one column and saved the layout. The layout name comes on to the selection screen parameter which i have defined on the selection screen.
PARAMETERS: p_vari LIKE disvariant-variant. " ALV Variant
i have made the i_save = 'A' and is_default = 'x'. and also used other function modules reg. Variants.
but if i select the layout variant in the selection screen and execute it is not working . the hidden column also coming on the output.
But if the select the layout variant on the output of the report from the icon select layout it is working fine. the column which i have hidden is not coming. it is perfect. why it is not working when i select the variant in the selection screen.
Regards,
Rose.

Hi,
Please try this code
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
w_variant-report = sy-repid.
* Function module to show the variant of a ALV report
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant = w_variant
      i_save     = 'A'
    IMPORTING
      es_variant = w_kvariant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 2.
    MESSAGE ID sy-msgid TYPE 'S'      NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
    p_vari = w_kvariant-variant.
ENDIF.
END-OF-SELECTION.
MOVE w_variant TO w_kvariant.
    MOVE p_vari TO w_kvariant-variant.
    MOVE sy-repid TO w_kvariant-report.
*   Function module to check the variant existence
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
      EXPORTING
        i_save     = w_save
      CHANGING
        cs_variant = w_kvariant.
    w_variant = w_kvariant.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
      i_callback_program          = sy-repid
      i_callback_pf_status_set    = 'SET_PF_STATUS'
      i_callback_user_command     = 'USER_COMMAND'
      i_callback_html_top_of_page = 'HTML_HEADING'
      i_grid_title                = text-t06
      i_grid_settings             = wa_grid_set
      is_layout                   = wa_layout
      it_fieldcat                 = t_fieldcat
      i_save                      = 'X'
      is_variant                  = w_variant
      is_print                    = wa_print
    TABLES
      t_outtab                    = t_header
    EXCEPTIONS
      program_error               = 1
      OTHERS                      = 2.
IF sy-subrc <> 0.
    CASE sy-subrc.
      WHEN 1. RAISE program_error.
      WHEN 2. RAISE others.
    ENDCASE.
ENDIF.
Regards
Krishna
Edited by: Krishna Gowrneni on Apr 17, 2009 5:27 PM

Layout variant is not working in background in ALV report

Hi,
I have one LAV report to send the report output through mail in foreground and backgroud.Final internal table is having 46 fileds to display the output.But here user is saving the layout variant and sending that layout variant output to mail id in excel format with zip file.Its working in foreground.But in background its not working.Even if we select the layout variant,its sending all the 46 fileds to mail.
here we have used the below FM to update the fieldcat itab.
CALL FUNCTION 'REUSE_ALV_GRID_LAYOUT_INFO_GET'
    IMPORTING
      et_fieldcat   = it_fieldcat[]
      es_variant    = v_disvariant
    EXCEPTIONS
      no_infos      = 1
      program_error = 2
      OTHERS        = 3.
In for ground NO_OUT = 'x' for non selected fields and NO_OUT = ' ' for selected fields.
But in background NO_OUT = ' ' for all the fileds, even if we select the layout variant.
Please suggest me with the solution.
Regards,
Jayaram

hi ,
Do according to this
SORT t_ekbe by belnr.
if t_ekbe[] is not initial .
      SELECT MBLNR
        BWART
        SMBLN
        ERFMG   " This is the new added field
        erfme     " This is the new added field
      INTO CORRESPONDING FIELDS OF TABLE t_mseg
    for all entries in t_ekbe
      from mseg
      where mblnr = t_ekbe-belnr
      AND   bwart = '101'.
endif.
after this
loop at t_ekbe .
loop at t_mseg where mblnr = t_ekbe-belnr .
t_ekbe-ERFMG = t_mseg-ERFMG .
t_ekbe-erfme =   t_mseg-erfme .
modify t_ekbe transporting ERFMG erfme .
clear t_mseg .
endloop.
clear t_ekbe .
endloop.
Regards
Deepak .

How to create a variant to a maintenance view (trans: SM31)

Hi gurus.
I have created a maintenance view (called z_jest). By running it from SM31 there is a variant option. However, I am not able to create the variant which I want to filter a selection upon in this transaction.
I have even looked into transaction SE54 and created a variant for the maintenance table view there( called z_jestv). Then going back to transaction SM31 and view z_jest, i push 'Variant' radiobutton and type as variant: 'z_jestv', I only get the message: "Variant z_jestv for object z_jest does not exist".
Can anybody please advice on how to create and/or connect the variant to the maintenance view?
Regards LL.

Hi Mahalakshmi
Thanks for reply.
When I look into the procedure, there is a prerequisite: "The basis dialog for which the maintenance variant is created already exists."
I am a little bit unsertain if I miss this 'Basic dialog'. Can you please advice on how to check / create this 'basic dialog' before I go on to create the variant. (I need this 'basic dialog' as input in the procedure you sent.)
(Note: I have already created a 'maintenance dialog' for the view, but I have a feeling, that is something different...)

How to Save Multiple Variants for a Report at a time?

Hi Experts,
I have a report in one server and I have copied the same into another server.
And now I also have to copy the variants of that report.
There are totally 192 variants for the report. So, is there any easier way to copy all those variants for the new report that I have created, rather than re-creating the variants one-by-one manually.
Note:There is no connection to both the servers. So I cannot transport them.
Thanks in advance.

Basis can do a export and import transport, still if don't have connection between boxes.
or
check this
http://www.sap-basis-abap.com/abap/copy-program-variants-from-one-to-another.htm
a®

Error while saving FYV : Gaps in financial year variant periods

Hello Experts,
We are getting an error while saving a new FYV as:
Gaps in financial year variant periods XY
Message no. FGV556
Diagnosis
The period specification has gaps. The periods must be sequentially numbered without any gaps.
System Response
Only a correctly defined period assignment can be saved.
Procedure
Define the periods with consecutive numbers.
Details: The new FYV has 52/53 weeks as posting periods depending on calendar year.
For example, we are trying to define Fisc 2009 as follows. (Fiscal year 2009 = Nov 01 2008 to Oct 31 2009).
Month-Day-Period-Yearshift
11     ---     7     ---     1     ---     +1
11     ---     14     ---     2     ---     +1
11     ---     21     ---     3     ---     +1
11     ---     28     ---     4     ---     +1
12     ---     5     ---     5     ---     +1
12     ---     12     ---     6     ---     +1
12     ---     19     ---     7     ---     +1
12     ---     26     ---     8     ---     +1
12     ---     31     ---     9     ---     +1
1     ---     3     ---     9     ---     0
1     ---     10     ---     10     ---     0
1     ---     17     ---     11     ---     0
1     ---     24     ---     12     ---     0
1     ---     31     ---     13     ---     0
2     ---     7     ---     14     ---     0
2     ---     14     ---     15     ---     0
2     ---     21     ---     16     ---     0
2     ---     28     ---     17     ---     0
3     ---     7     ---     18     ---     0
3     ---     14     ---     19     ---     0
3     ---     21     ---     20     ---     0
3     ---     28     ---     21     ---     0
4     ---     4     ---     22     ---     0
4     ---     11     ---     23     ---     0
4     ---     18     ---     24     ---     0
4     ---     25     ---     25     ---     0
4     ---     2     ---     26     ---     0
5     ---     9     ---     27     ---     0
5     ---     16     ---     28     ---     0
5     ---     23     ---     29     ---     0
5     ---     30     ---     30     ---     0
6     ---     6     ---     31     ---     0
6     ---     13     ---     32     ---     0
6     ---     20     ---     33     ---     0
6     ---     27     ---     34     ---     0
7     ---     4     ---     35     ---     0
7     ---     11     ---     36     ---     0
7     ---     18     ---     37     ---     0
7     ---     25     ---     38     ---     0
8     ---     1     ---     39     ---     0
8     ---     8     ---     40     ---     0
8     ---     15     ---     41     ---     0
8     ---     22     ---     42     ---     0
8     ---     29     ---     43     ---     0
9     ---     5     ---     44     ---     0
9     ---     12     ---     45     ---     0
9     ---     19     ---     46     ---     0
9     ---     26     ---     47     ---     0
10     ---     3     ---     48     ---     0
10     ---     10     ---     49     ---     0
10     ---     17     ---     50     ---     0
10     ---     24     ---     51     ---     0
10     ---     31     ---     52     ---     0
The above entries cover all the dates in calendar year 2009, that is, Jan 2009 to Oct 2009 is covered by periods 10 to 52 and Nov 01 2009 to Dec 31 2009 is covered by period 1 to 9 of the following fiscal year 2010.
Inspite of making sure that all the days of 2009 are covered by periods 1 to 52. We are still unable to save the FYV.
Please help!
Susan

Hello, I am getting this error while saving the FSV. My FSV is based on Weeks. Below is what I am inputting for this. Other details are Calender Year - 2017, No. of posting periods - 53, checked year dependent. Also, I have FSV for previous years also where weeks are 52 but configured as 53. So, hope that this is not creating this issue. Solicit your early response.
Month
Day
Period
Year Shift
1
7
1
0
1
14
2
0
1
21
3
0
1
28
4
0
2
4
5
0
2
11
6
0
2
18
7
0
2
25
8
0
3
4
9
0
3
11
10
0
3
18
11
0
3
25
12
0
4
1
13
0
4
8
14
0
4
15
15
0
4
22
16
0
4
29
17
0
5
6
18
0
5
13
19
0
5
20
20
0
5
27
21
0
6
3
22
0
6
10
23
0
6
17
24
0
6
24
25
0
7
1
26
0
7
8
27
0
7
15
28
0
7
22
29
0
7
29
30
0
8
5
31
0
8
12
32
0
8
19
33
0
8
26
34
0
9
2
35
0
9
9
36
0
9
16
37
0
9
23
38
0
9
30
39
0
10
7
40
0
10
14
41
0
10
21
42
0
10
28
43
0
11
4
44
0
11
11
45
0
11
18
46
0
11
25
47
0
12
2
48
0
12
9
49
0
12
16
50
0
12
23
51
0
12
30
52
0
12
31
1
+1
Thanks
Deepankar

How to find out list of variants in TVARV table

hi!
can anybody can guide me on the following issues? plz
How to list all variants in TVARV table?
How to find out any Z* programs that writes to TVARV table, using the variant name?
How to find out the programs which are reads the TVARV data into a program variant?
Thanks & Regards,
vijay

Or some help might be useful:
http://help.sap.com/saphelp_47x200/helpdata/en/c0/98037ae58611d194cc00a0c94260a5/frameset.htm
Regards,
Subramanian V.

Variants in forte

Similar Messages

Maybe you are looking for