Recent content by MollyMoon

Hello, I searched the FAQ's and found a similar problem (thread216-7131253) but couldn't get it to work for me. I am trying to set the value of one hidden field ("optionsChanged") as part of a function that also stores the values of all the fields on the form in a cookie prior to...

Knob: To answer your last question, "Are all capture files during the script run showing this problem, or just certain files at certain times?", this only happens when the capture files are large (as mentioned earlier). KentIsland: Thanks for the input. I looked into this, and we...

Hi Knob, Yes, we are using a script (sorry, I should have mentioned that earlier). The capture file is not opened and closed repeatedly, however, the script turns capture on and off anywhere from 2 to 4 times within the script (depending on how many reports we need to run). This is because...

We are having a problem with the capture process in ProComm, and I'm wondering if anyone has heard of this before. We use ProComm to dial and login to a remote system, then run a report, capturing the data from the report. This works well with the exception of when the file is particularly...

Thanks, that worked. The help file indicated that the connection directory should be in quotes as well, which is where I had trouble. (Although it also refers to PW4 so it is clearly outdated).

The help files indicate: "You can launch Procomm Plus with the PW4 command line parameter. In addition, you can include command line arguments which control how Procomm Plus behaves once it is launched....The PW4 command line parameter always follows this form: PW4 [argument] [argument]...

Well, I changed the connection directory to point to PW5.dir on the machine where our app is running. This is an empty directory; it has never been used. Things were fine for a day (we saw no similar errors) but this morning we got the "error reading file" on PW5.dir. Any thoughts...

I can appreciate the potential problems of accessing the connection directory across the network, but I still wonder why we never experienced this problem until a week or so ago, and now we get it constantly.

Knob, Thanks for the info. That's what I was trying to find out -- if ProComm was accessing the connection dir on launch. That explains part of the problem, but why it is failing in its attempt is still an issue. The connection directory being referenced is not the default(PW5.DIR) but a...

I do have the source for my script; I helped write it. That is how I know it isn't relying upon the Connection Directory in any way. Thanks for the thought on the Sys Admin -- come to think of it our guy did an upgrade to both computers on which this problem is occurring. Because we are...

We have recently begun experiencing a problem upon launch of ProComm, where we get various errors, all which reference our connection directory: Error writing to File... Error reading File... Error allocating memory for... The problem is that we are NOT USING the connection directory when...

Can anyone explain to me what the impact is of changing pausechar from the default (tilde)? ProComm help files indicate it should not be changed "unless you have a specific reason to do so". What reasons are there for changing this? I have inherited code that creates an aspect...

It's interesting that you had to restart Windows. We've found that the problem does clear itself up eventually. There seems to be some amount of time (we have been unable to pinpoint a specific length) whereby if we tell our app not to use that modem, then reinstate it a while later, the...

I will add the pause 15 as you recommend. Do you know what error is returned by ProComm under this circumstance? I'm assuming I can trap it with $CNCTMSG... Have there been any updates to v4.8? Thanks much for all your help.

As a matter of fact ProComm is opened and closed repeatedly, and I have seen the behavior you mention with the globe icons in the system tray not going away. In fact this seems to happen quite frequently. They disappear if you move the mouse over them. The script being run closes ProComm as...