View Single Post
  #3  
Old 09-29-2004, 07:23 AM
hurcane hurcane is online now
Registered User
 
Join Date: 09-28-2004
Posts: 4
kevina,

Thanks, but my problem is not in the regular expressions. My problem is in using the macros set by the process files action.

The process files action automatically sets some macro variables. From the help, these macros are:
PROCFILES_FULLPATH
PROCFILES_FILENAME
PROCFILES_ROOT_DIR
PROCFILES_FILE_DIR
PROCFILES_COUNT

The replace in files action has an input file option and an output file option. I have entered %PROCFILES_FILENAME% in these two fields.

My search/replace text has no square brackets. The problem I am seeing is that the %PROCFILES_FILENAME% value is being parsed rather than treated as a literal value.

Here is the log from my test...
Building project step 'Build database'...
Building project step 'Change to views folder'...
Step default property 'Path' = 'c:\dev\database\views'
Building project step 'Process views'...
Loading a list of matching files...
Processing file 1 of 1524: [dbo].[GetBankAccount].sql...
Building project step 'Make ALTER into CREATE'...
Step default property 'FileIn' = '..sql'
Failed to open '..sql': The system cannot find the file specified.
Step 'Make ALTER into CREATE' failed
Build ended.

Note that the process files step seems to be working fine. It's the FileIn property, which I have set to %PROCFILES_FILENAME%, that is getting corrupted.

I would do a "replace" function on the macro to double up the square brackets, but I don't know what kind of action(s) I could use to do that.
Reply With Quote