<i><font color="#663300">Sorry about dragging up version 3.0, but I need some opinions - and I think this would apply to 6.0 and up.
We have a "very large" project that has been sold (<g>) to another customer, and they want us to maintain it seperately from the current one.
What I would like do is take the current source directory c:cdbk30project1 and copy all the files in here to c:cdbk30project2.
The problem is that there are lots and lots of references - like #INCLUDEs that point to the original directory.
Does anyone have any nifty solutions, except for us to go through everything piece by piece and change these.
Cheers,
Mark</font></i>
I went through something like this before. Backup your files and try these...
1. Try putting the project into the c:cdbk30project2 then issue the =startcb(.t.) command. This will probably update most, if not all the directory paths in the include files. Check the error log and update what you find.
2. Then use the setincl utility, for the classlibs that have include files. Compile and check the error logs again.
3. After this, you can also use the codefind.app utility. It basically goes through every prg and vcx to look for a specific string such as cdbk30project1. Write them down then change them 1 by one. It beats "looking for a needle in a haystack".
Hope this helped.
©2002 Allen Pascual |
