RE: VARPG question

You can look at the project files, these are .ivg files in the VARPG
project directory.
Open these with WORDPAD and change the source directory location to the new
location.
That will allow VARPG to find them there when you open the GUI designer

Here is how a typical ivg file looks like

-VRPG300ProjectInfo
sourceDir=D:\WDSC\test2fld   <---    change this line
targetPgm=test2fld.EXE
buildOpts=0 /GL 10 /Ti /RT /SVC /SVG /L /LX /LC /LD /LE /LV /LM2
/ICONdefault
buildJavaOpts=0 /GL 10 /RT /SVC /SVG /JC "javac.exe" /CHANGEFONTSIZE /L /LX
/LC /LD /LE /LV /LM2
description=

Claus Weiss Visual AD tools, email: [email protected]
Dept XF6 IBM Canada Lab tie 969-3987 Phone(905)413-3987 FAX(905)413-4850
Greetings from Toronto
Rational Software System i - Ecosystem Team


                                                                           
             "Kurt Anderson"                                               
             <kjanderson@highs                                             
             mith.com>                                                  To 
             Sent by:                  "CODE/400 Discussion &amp; Support" 
             code400-l-bounces         <code400-l-Zwy7GipZuJhWk0Htik3J/[email protected]>            
             @midrange.com                                              cc 
                                                                           
                                                                   Subject 
             07/09/2007 04:59          RE: VARPG question                  
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
                 "CODE/400                                                 
             Discussion &amp;                                              
                 Support"                                                  
             <code400-l@midran                                             
                  ge.com>                                                  
                                                                           
                                                                           




Probably not much help here, but can you right click on the project and
Move it to a one-word folder?  As it turns out, all of our projects are
in one-word folders.  As an fyi, I know we've had an issue with
performing a pointer installation to a multi-word folder (unlike local
installations, which seem to work fine).


Kurt Anderson
Application Developer
Highsmith Inc

-----Original Message-----
From: code400-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]
[mailto:code400-l-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf Of Dave Shaw
Sent: Monday, July 09, 2007 12:36 PM
To: code400-l-Zwy7GipZuJhWk0Htik3J/[email protected]
Subject: VARPG question

We have an old, complex VARPG application that I have to make some
changes to.  Way back when (before I was even hired here), someone
decided to put it in a directory named VARPG Source.  I'm finding that
the blank in the directory name causes some things in the development
environment to not work, including the Duplicate Project function.  I
don't see a way to change the directory that the projects point at, so
just copying the files doesn't work, and neither does renaming the
directory.  Does anyone have any ideas?

Thanks!

Dave Shaw
Mohawk Industries

_______________________________________________
This is the CODE/400 Discussion &amp; Support (CODE400-L) mailing list
To post a message email: CODE400-L-Zwy7GipZuJhWk0Htik3J/[email protected] To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request-Zwy7GipZuJhWk0Htik3J/[email protected] Before posting, please take a
moment to review the archives at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries discussion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsci-l


_______________________________________________
This is the CODE/400 Discussion &amp; Support (CODE400-L) mailing list
To post a message email: CODE400-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries discussion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsci-l



_______________________________________________
This is the CODE/400 Discussion &amp; Support (CODE400-L) mailing list
To post a message email: CODE400-L-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries discussion has it's own mailing list.
Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsci-l