Francesco
11th January 2005, 17:42
It seems to me that every time I program API routines in a different Baan environment, I run into unspecific issues that I never encountered before.
Ironically, I had the least problems on a 5b system, a version that has known issues with API.
Does anybody have any insight in the definite requirements for a working API environment?
For IVc2 (my current pain) I would say:
ottstpstandard: 4/12/29
ottstpapihand: 04/11/05
I am not sure about minimum porting set requirements and such. Rather than specific solutions (i.e. 10923), I am hoping that we can produce a set of components per version and maybe bundle them here as a custom solution?
mark_h
11th January 2005, 19:37
I do not think this is possible - it varies from version to version, extension to extension, etc. I have had new session objects stop the API function servers from working. Other problems have been caused by porting sets and tools updates. I am currently running two different versions for 4c4 along with two different porting sets. Maybe a set of recommendations, but then how specific would they need to be? Then who would update it to keep it current?
Just some thoughts.
Mark
Francesco
11th January 2005, 19:47
So let me pop another question.
What specific components does the API actually use?
There should be a straight-forward version independant answer to that one.
NPRao
11th January 2005, 21:48
The object info tells me that you would need BaaN 4-GL, include and porting sets.
Date : 01-11-05 [11:51, Ame] Object information Page : 1
BaanERP_Tools7.3a Company : 000
--------------------------------------------------------------------------------
Object Information
--------------------------------------------------------------------------------
Path
--------------------------------------------------------------------------------
Object = ottstpapihand
Pathname = /app/lms/lmss/opt/bse/tools/tt7.3_a/ottstp/ostpapihand
--------------------------------------------------------------------------------
Header
--------------------------------------------------------------------------------
Magic = [_bic_dll_]
relno = 72
product ID = 1005
obj_revision = 1
object_flags = 8=DLL
--------------------------------------------------------------------------------
Used DLL's
--------------------------------------------------------------------------------
Used DLL = ottstp_stddll
--------------------------------------------------------------------------------
DLL Hints
--------------------------------------------------------------------------------
function __initialize.process (Hint: Located in DLL: ottstp_stddll)
function message (Hint: Located in DLL: ottstp_stddll)
--------------------------------------------------------------------------------
Ident String
--------------------------------------------------------------------------------
@(#)/d2/reger_build/bse/tools/tt7.3_a_bld/pttstp/pstpapihand0, 04/11/22 [10:20],
@(#)-DREL6_2
@(#)-DBAAN73
@(#)-DREL7_2
@(#)4GLE_BUILD_RegerSP1_1188 -- bic_global@@/main/bugfix73asp1/6
@(#)4GLE_BUILD_RegerSP1_717 -- bic_bshell@@/main/bugfix73asp1/13
@(#)4GLE_BUILD_RegerSP1_717 -- bic_object@@/main/bugfix73asp1/2
@(#)4GLE_BUILD_RegerSP1_1188 -- bic_commands@@/main/bugfix73asp1/3
@(#)4GLE_BUILD_RegerSP1_717 -- bic_event@@/main/bugfix73asp1/1
@(#)4GLE_BUILD_RegerSP1_717 -- bic_key@@/main/bugfix73asp1/1
@(#)4GLE_BUILD_RegerSP1_1188 -- bic_shell@@/main/1
@(#)bic_shell, 08-1994/R1, Copyright (c) Baan International b.v.
@(#)4GLE_BUILD_RegerSP1_1188 -- bic_fork@@/main/bugfix73asp1/1
@(#)ttstpapihand ttB50a3 apollo Rev.No. 3 16 Dec 96 pietk
@(#)ttstpapihand ttB50a4 saturn Rev.No. 4 07 Jan 98 pietk
@(#)ttstpapihand ttB50b saturn Rev.No. 34 27 Jul 01 tvpoortv
@(#)ttstpapihand tt7.0a saturn Rev.No. 6 11 Aug 99 gvdwal
@(#)ttstpapihand tt7.0a1 saturn Rev.No. 16 09 Apr 01 gvdwal
@(#)ttstpapihand ttB50b ping Rev.No. 79 12 Dec 03 gvdwal
@(#)ttstpapihand tt7.6a ping Rev.No. 3 07 Nov 03 gvdwal
@(#)ttstpapihand tt7.3asp1 ping Rev.No. 19 05 Nov 04 gvdwal
@(#) December 1998 : Performance improvements
@(#)handle.subproc for menus inprofed
@(#)stpapi.clear function added
@(#)DF84124 : Some problems solved with insert/update on
@(#) synchronized dialog sessions
@(#) October 1997 : Added argmuments (do.update) in functions
@(#) insert/update/delete
@(#) October 1997 : Added function get.mess.code
@(#) December 1997 : After update/insert new values are taken back
@(#) December 1997 : Solved problem with multiple forms
@(#) December 1997 : Solved problem with more than 1 session
@(#) April 1998 : Session created in separate process group
@(#)DF19590, 1998/10/05: Baan is not responding after delete action
@(#) December 1998 : Update and save action combined in 1 call
@(#) December 1998 : Performance improvements
@(#)DF79668, 1999/04/20: Remove subprocesses when parent is stopped
@(#)DF79857, 1999/04/29: Only fields filled with put functions
@(#) are used in fs
@(#)TCS100-59768 : Last message code now also set in
@(#) stpapi.find(), stpapi.browse.set(),
@(#) stpapi.change.view(), stpapi.start.set(),
@(#) stpapi.browse.view()
@(#)TCS100-60268 : Parsing of reply in SendAndReceiveToProcess
@(#) simplified & improved
@(#)DF105485, 2001/01/29: Afs.log is written though AFSLOG is not set
@(#)DF116502, 2001/08/30: the delete function don't support do.save=false anymo
@(#)DF201594, 2001/09/19: get.fields will now also log the retrieved fields
@(#)DF117374, 2001/10/31: Index out of dims error when session started twice vi
@(#)DF201584, 2001/11/06: Synchronization problem when no put is done on the ke
@(#)DF118671, 2002/05/14: field data is cleared when blocking session finishes
@(#)DF126202, 2002/07/17: additional check needed to clear field data
@(#)DF127763, 2002/09/03: Second synchronize dialog fails
@(#)DF127407, 2002/09/18: hanging sessions when an end() is encountered
@(#)DF209385, 2002/09/18: fixed by 127407.
@(#)DF127407, 2002/10/17: additional enhancements for when processes are gone
@(#)DF131940, 2002/12/13: mode sync dialog set to undercase
@(#)DF127102, 2003/01/08: synchronize cont.process
@(#)DF131892, 2003/01/10: FS in 4GL caused hanging sessions
@(#)DF212222, 2003/01/22: Hanging OW because of exit.child
@(#)DF212722, 2003/02/21: Only get next event if there is one after exit.child
@(#)DF136040, 2003/04/23: Only remove event if it is a bucket event
Date : 01-11-05 [11:51, Ame] Object information Page : 2
BaanERP_Tools7.3a Company : 000
--------------------------------------------------------------------------------
Ident String
--------------------------------------------------------------------------------
@(#)DF136114, 2003/04/23: send define enum answer to child
@(#)DF213495, 2003/05/09: small changes related to starting sess.
@(#)DF217484, 2003/12/12: Use of NULL pointer error during end.session
mark_h
12th January 2005, 21:22
I only know of two libraries - ottstpapihand and ottstpapidaemon. I am not even sure what the ottstpapidaemon is for, or if it is even related.
My current working components:
Production/test
Baan Version: Baan 4C4 service pack 16(I think)
Client version: B40C.74
Porting Set : 6.1c.07.01
Port no. : PA.2272
Service Pack Testing
Baan Version: Baan 4C4 service pack 17
Client version: B40C.74
Porting Set : 6.1c.07.04
Port No. : PA.2503
Just noticed when I use bshcmd6.1 -v that the port no. is different on both boxes - is that relevant? I am not sure what all else may go into getting stpapi commands working. Are you holding out on us Francesco? :)
Mark
Francesco
14th January 2005, 19:04
I'm not holding out, I just think I have an idea of where this is going.
The last time a client of mine called Baan support about an API issue, they had the poor fellow install two service packs and a few dozen additional solutions.
So far I've been able to solve issues here locally by just mixing and matching standard program components.
mark_h
14th January 2005, 20:17
Only once has Baan asked that we do something other than a new tools update - they had us update the porting set. Usually we solve it like you do. In the case of the porting set Baan comment was something like - YOUR RUNNING that version and WHAT client. I think we had went a couple years without doing any porting set or client updates. This is just one of those things that make API stuff fun!!!
Mark
lbencic
14th January 2005, 21:47
On an unrelated subject I was checking the Baan support site, ran into solution #74732. An interesting read that seems to have been updated in the last couple days. Check out the bottom where they recommend a freeware external scripting program for automating (www.hiddensoft.com).
This solution is a good place to start if you are having afs problems, and there's a link on there to the solution that holds the latest versions.
According to this, the objects SSA support wants to know about for afs's are:
ottstpapihand
ottstpapiserver (if it exists)
ottstpstandard
ottstpamdll
If printing:
ottstpsplopen
ottstpsplclose
ottstprepdll
mark_h
14th January 2005, 22:50
Interesting - never heard of this product. May have to take a look at it and see what it does later on.
Mark
p.cole
15th January 2005, 01:10
I tested AutoIT (suggested by BGS) when trying to automate the session "Product Configurator" (tipcf5120m00) about a year ago. As far as I can remember it didn't work with display fields in Baan Windows because the bw client draws directly onto the application window (device context).
It does work when "proper" Windows controls have been used to develop the application.
Kingsto88
8th June 2005, 09:58
Hi,
I have downloaded autoIT but I need to know how to use it to replace AFS. For eg. How can I pass in the fields to ticpr2210m000 so that it will run the cost price calculation for that item.
thanks and regards