Recent content by tedzap

My problem ended up being related to domain privileges. Doesn't sound like this would be applicable to yours. Best, -Ted

Thanks, I'll give this a try.

Hello, Is there a way to disable the "X" in the top right hand corner of the ProComm window? Every once in awhile a user will lock up a database file and then "X" out of the window. At that point the only recourse is to reboot the server. If the X in the top right of the window could be...

Hello, thought I would report back my findings in this matter. The folks in question have a domain set up, and he was logging on as a domain user with administrative privileges. This is sufficient for him to load many software programs (such as office) but not ProComm. In order for him to...

Thanks. I shot him that question, he said he will let me know when he gets another look at it (hopefully tomorrow). The salesman had already grabbed it and left the building.

Thanks for the replies. At least there probably isn't any fundamental problem with SP3. He *is* a member of a domain, but has never run into any such security issues before. I am not "domain savvy", have never used them. He also says the user he is installing from *does* have admin...

Hello, This is not programming related, but if there is a problem between SP3 and ProComm I would think it general interest to the group. I thought someone here might have seen this or have ideas. I have a customer who has picked up a new laptop that has XP/SP3 installed. He has tried...

thanks for all the replies. The person I am doing this for ran a session over the weekend. he made dozen's of file captures and after 4 days it hung (same session). I have now compiled it with "compile for debug" and also selected "create map file" and "include line numbers". I have not used...

I expect that you are right about it getting hung in the called procedure. Yes, I am sure about the number of spaces always being constant, I am writing the code on that end as well. The script was having the same problem before I inserted the FOREVER qualifier on the WAITFOR. I put it in...

Thanks for the response... I tried putting in the "when clear" statement, but that simply made it a "one shot" kind of trigger. in other words, when the trigger was seen the first time it worked properly. at the end of that procedure, the "when clear" seems to turn off the loop that is...

The below is a slightly cleaned up version of what I am trying to do. To summarize, I want to have the script watching for the *CSV TRIGGER* string, grab the file name, open a capture file using that name, capture the data, close the file, clean up after itself. All seems to work as I wish...

Although it may not be needed for ProComm, there does appear to be a "compatability mode" in Vista. Gleaned from the internet (I haven't seen a Vista machine yet): "To configure the compatibility mode for an application, just locate the installation directory and right click on the .exe...

I have walked the customer through the steps you recommend. Running the Setup.exe directly form the CD folder seems to work. I also had him compile a script (successful) and he went ahead and created a connection to a server. Right now I do not see any compatability problems, will wring it...

In his words: "Vista won't even launch the the installation program. The welcome screen comes up, and you click on install, then Vista asks you if you trust the program, and you click yes, then nothing happens" If you have any ideas about something to try, I can walk him through it...

I have a customer who said that "My ProComm CD will not run on Vista". I have not had my hands on a Vista machine yet. I did a search here on "vista" but it came up empty. has this topic been addressed? anyone know anything about this? thanks -ted