Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
WebBatch
 | |
| |
| |
| |
|
- !!NEWSFLASH!!
- CGI Forms to Change NT User Passwords
- Event ID 1000 in Server log
- Executing Webbatch from Browser
- Form Variables Empty
- Is Webbatch an ISAPI product
- ISPs and WebBatch
- LED in WebBatch
- Mail.web Character Limit
- NCSA Log report maker script
- Netscape is attempting to download Webbatch
- ParseData Limitations
- Perflib Performance Data Problem
- Return the Filename Associate with Form Data
- Security and User Authentication
- Variable Name Not Passed by IE6 or IE7
- Webbatch and Printing to Local Printer
- Webbatch and REXX
- WebBatch and Server Platforms Supported
- WebBatch and Windows 2003 Server
- Webbatch on MS Personal Web Server
- WebBatch on Virtual Servers
- WebBatch Security
- WebBatch vs WinBatch
- WebBatch Web Host
- WebParamData Fails with DIV Tag
- WebParamSet and TimeOut Error
- What is WebBatch and How Does It Work
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
ParseData Limitations
Keywords: parsedata param0 parameters
Question:
I am using WebBatch in a test environment and came across the ParseData limitation.Param0 seems to find the total parameters passed, but I am unable to get past the Ninth Item. I see that you have documented the limitation, but is there a possibility to extract the entire string passed.
Answer:
WinBatch 2003F and older: ParseData was limited to 9 items.WinBatch 2003G and newer: ParseData no longer has a limit of 9 parameters. The tenth parameter now gets stored as "param10", etc.
Article ID: W12454
Filename: ParseData Limitations.txt
File Created: 2013:01:18:15:59:34
Last Updated: 2013:01:18:15:59:34