Replies

Thanks for the response. I really appreciate your time.

You are right about declaring a variable as Public in the declarations section of the module makes the variable available throughout the module. I had done this when declaring my Wrd and doc variables. However, the references to the objects are broken once I leave that module. I’m assume that simple values persist, but references to objects do not. Here is generally what happens:

Procedure 1 calls Procedure 2. Procedure 2 sets Wrd and doc to their objects and transfers content to those objects. Procedure 2 then ends and control is returned back to Procedure 1. I would have thought that the reference would have persisted back to Procedure 1. This is not the case.

I even changed the code around so that the references were set in Proc 1 and the processing using those references occur in Proc 2. Either way, I lose the references when moving between procedures.

Does anyone have any other ideas?

As usual, I didn’t give enough information. Whenever I do give a lot of information, I feel like I’m rambling…

The decision I came to is that I need to split the data into multiple objects. So I’m working on that now. Thanks for the input.

As usual, I didn’t give enough information. Whenever I do give a lot of information, I feel like I’m rambling…

The decision I came to is that I need to split the data into multiple objects. So I’m working on that now. Thanks for the input.

I believe that I found a fairly good primer for FTP batch files here. This think this was written for AS/400 programmers, but it is a good article for anyone. Thanks to those who responded.

Now, does anyone have a good vbs script?

I believe that I found a fairly good primer for FTP batch files here. This think this was written for AS/400 programmers, but it is a good article for anyone. Thanks to those who responded.

Now, does anyone have a good vbs script?

Could you provide some more information on this. We use WS_FTP already.

Could you provide some more information on this. We use WS_FTP already.

I tried to search for past posts prior to posting my own, and didn’t find anything.

I am aware that WinXP has its own command-line FTP engine. I’ve used it many times. However, when I’ve tried to write a batch file to automate it, I get the FTP session up, but the user and pwd commands are not processed. Apparently, I’m doing something wrong, because I know that it can be done within a text file.

I tried to search for past posts prior to posting my own, and didn’t find anything.

I am aware that WinXP has its own command-line FTP engine. I’ve used it many times. However, when I’ve tried to write a batch file to automate it, I get the FTP session up, but the user and pwd commands are not processed. Apparently, I’m doing something wrong, because I know that it can be done within a text file.

Hi Stuart– Thanks for the reply.

I would have thought so, but I cannot find out how to take control of it. I cannot open Properties since I don’t have access and right-clicking on it brings up no useful choices. Do you (or anyone else) have any suggestions on how (and if, for that matter) I can do this?

I’m not sure what you want, but I’ve included a screen shot of my local GPO and what templates are installed.

I’m not sure what you want, but I’ve included a screen shot of my local GPO and what templates are installed.

I have all the documentation I can find. The operative word you used is “should”. As far as I know, I done everything that needs to be done to return AU to client configurability, but it is still grayed out. If you know of anything else that I haven’t tried, I’d be eternally grateful.

I have all the documentation I can find. The operative word you used is “should”. As far as I know, I done everything that needs to be done to return AU to client configurability, but it is still grayed out. If you know of anything else that I haven’t tried, I’d be eternally grateful.

Hey Pat. Thanks for joining the conversation.

Yes, you are right. Clicking the Save password checkbox will overcome having to type in your password each time–ON MOST ODBC CONNECTORS. This is an AS/400 connector–and it is a little flakey. The Save password checkbox doesn’t, and creating a file-based connection (*.dsn) is highly unstable. You have to use a machine-based connection, which really sucks if your app needs to be available on multiple desktops.

I appreciate everyone’s responses. Hopefully, someone will come up with a snippet of coding that will do the trick. I tried creating a ConnectionString, complete with UID and PWD, but didn’t know how to tie it to an already linked table, OR delete the link with the table and create a ConnectionString that will connect to an existing AS/400 file.