Does TMS Scripter support X64 platform?

I use TMS workflow(scripter included),under x32 platform,everything is ok;but when I switch to x64 platform,all components work normal except Scripter,which raises strange errors.

My question is:Does TMS Scripter support X64 platform?if it can,how to set up?

Scripter runtime supports all platforms supported by Delphi:  Win32, Win64, Mac OSX 32, Android, iOS. The visual IDE supports Windows (32 and 64).

But of course it doesn't mean it's 100% bug free. Can you please provide specific details about the problems you have and how to reproduce them?

Wagner Landgraf2016-03-31 15:43:17

well,I use scripter of tms workflow v1.9,a full version scriptert.

OS:win7 x86 32bit;
delphi:xe2 32 bit.
Following is simple test example,which can be  compiled under 32bitplatform,but can not under 64bitplatform.the import files(ap_*.pas) are original,not being generated by me.I guess the problem
seems staying at ap_DB unit.

unit Unit3;

interface

uses
  Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,
  Vcl.Controls, Vcl.Forms, Vcl.Dialogs,
  Vcl.ScripterInit,atscript,atScripter,
  {$ifdef WIN32}
    ap_Sysutils, ap_Classes,ap_DateUtils,
    //ap_Graphics, ap_Forms, ap_Dialogs,
    ap_StdCtrls, ap_Windows, ap_System,ap_StrUtils,
    ap_ExtCtrls, ap_ComCtrls,
    ap_Buttons,
    ap_Types,
    ap_ShellAPI,
    ap_ADODB,
    ap_Variants,
    ap_VarUtils,
    ap_VDBConsts,
    ap_WideStrings,
    ap_WideStrUtils,
    ap_FileCtrl,
    ap_IniFiles,
    ap_Consts,
    ap_Controls,
    ap_DBCommon,
    ap_DBCommonTypes,
    ap_DBConsts,
    ap_ActiveX,
    ap_DBCtrls,
  {$endif}

  ap_DB;
type
  TForm3 = class(TForm)
  private
    { Private declarations }
  public
    { Public declarations }
  end;

var
  Form3: TForm3;

implementation

{$R *.dfm}
initialization
RegisterScripterLibrary(TatDBLibrary);
{$ifdef WIN32}
  RegisterScripterLibrary(TatSysUtilsLibrary);
  RegisterScripterLibrary(TatDelphiSystemLibrary);

  RegisterScripterLibrary(TatClassesLibrary);
  RegisterScripterLibrary(TatTypesLibrary);
  RegisterScripterLibrary(TatStrUtilsLibrary);
  RegisterScripterLibrary(TatComCtrlsLibrary);
  RegisterScripterLibrary(TatStdCtrlsLibrary);
  RegisterScripterLibrary(TatExtCtrlsLibrary);
  RegisterScripterLibrary(TatControlsLibrary);

  RegisterScripterLibrary(TatWindowsLibrary);

  RegisterScripterLibrary(TatShellAPILibrary);
  RegisterScripterLibrary(TatActiveXLibrary);
  RegisterScripterLibrary(TatADODBLibrary);

  RegisterScripterLibrary(TatVariantsLibrary);
  RegisterScripterLibrary(TatVarUtilsLibrary);
  RegisterScripterLibrary(TatVDBConstsLibrary);
  RegisterScripterLibrary(TatWideStringsLibrary);
  RegisterScripterLibrary(TatWideStrUtilsLibrary);

  RegisterScripterLibrary(TatDBCommonLibrary);
  RegisterScripterLibrary(TatDBCommonTypesLibrary);
  //RegisterScripterLibrary(TatDBConnAdminLibrary);
  RegisterScripterLibrary(TatDBConstsLibrary);
  RegisterScripterLibrary(TatDBCtrlsLibrary);

  RegisterScripterLibrary(TatFileCtrlLibrary);
  RegisterScripterLibrary(TatIniFilesLibrary);
  RegisterScripterLibrary(TatConstsLibrary);
  RegisterScripterLibrary(TatDateUtilsLibrary);
{$endif}
end.

 

I'm sorry, but again this works just fine here, your test project you sent through e-mail also works on both 32/64 bits. I see now that you mention an old version, please always use the latest version of products.