Home
|
Forums
|
Contact
|
Search
|
Syndication
[login]
[create account]
Monday, November 25, 2024
slxdeveloper.com
Home
Search
Contact us
About slxdeveloper
Syndication
Community
Forums
(NEW!)
Newsletter Archive
Members
Your Profile
Submit Article
General
Administration
(6)
OLE DB Provider
Miscellaneous
(2)
Architect
VBScript
(9)
ActiveX Controls
(6)
How To's
(14)
.NET Extensions
(3)
External
OLE DB Provider
(12)
SLAPI (SlgxApi.dll)
SalesLogix COM
(1)
Web
ASP/ASP.NET
(2)
Web Services
Web Client
Downloads
Samples
(17)
Documentation
(7)
Utilities
(18)
Resources
SalesLogix
(3)
Programming
(1)
11/25/2024 4:38:29 AM
slxdeveloper.com Community Forums
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Architect Forums - Legacy Development
Forum to discuss SalesLogix legacy development including views, scripts, etc.. View the
code of conduct
for posting guidelines.
Forums RSS Feed
Back to Forum List
|
Back to Legacy Development
|
New Thread
View:
Dynamic
Flat
Tree
Search:
Author
Thread: Passing a value to a Script
Ian Fitzpatrick
Posts: 146
Passing a value to a Script
Posted: 21 Jun 06 11:22 AM
ventolin vs proair hfa
ventolin vs. proair
inhaler
fiogf49gjkf0d
I am on version 5.2.6. I have some long scripts with functions in them and I would like to divide them up to be more concise. I was wondering if there is a way to pass a value when calling another script. Like:
DOInvoke "Basic", "System:ING_Terr_ReState_UpIns" (value1, value2, value3)
or something.
Any advice is appreciated!
Thanks
[
Reply
][
Quote
]
Frank Chaffin
Posts: 475
Re: Passing a value to a Script
Posted: 21 Jun 06 12:19 PM
fiogf49gjkf0d
I use Application.BasicFunctions.GlobalnfoSet and Application.BasicFunctions.GlobalnfoFor
[
Reply
][
Quote
]
Jeremy Brayton
Posts: 491
Re: Passing a value to a Script
Posted: 21 Jun 06 1:19 PM
naloxone and naltrexone are examples of
narcan
vs naltrexone
fiogf49gjkf0d
Quote:
Originally posted by Frank Chaffin
I use Application.BasicFunctions.GlobalnfoSet and Application.BasicFunctions.GlobalnfoFor
Those are 6.x VBScript commands and if you're on 6.2.x there is an Application.GlobalInfo collection that is easier to manage than using those functions. The GlobalInfo* functions exist in Legacy and are mainly in BasicFunctions for backwards compatibility. One other function I use is GlobalInfoExists (or GlobalInfo.IndexOf("Blah")) to make sure the global variable is initialized properly, as an added layer of error handling. It'll most likely generate an error if you use GlobalInfoFor on a variable that hasn't been set but I tend to be anal when it comes to these types of checks. 5.x's error handling is vastly different than VBScript so it made sense when I was in Legacy land to litter my code with as many error handling routines as I could.
[
Reply
][
Quote
]
Page 1 of 1
You can subscribe to receive a daily forum digest in your
user profile
. View the site
code of conduct
for posting guidelines.
Forum RSS Feed
-
Subscribe to the forum RSS feed to keep on top of the latest forum activity!
slxdeveloper.com is brought to you courtesy of
Ryan Farley
&
Customer FX Corporation
.
This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.
code of conduct
|
page cache (param): 11/25/2024 4:41:31 AM