Auto-generated Filename is too long in DBCompare Report
Posted: Thu 01 Mar 2018 15:59
Hi
I'm trying to generate a report that includes data, but it errors because the temporary binary files are too long:
And here's what the auto-generated filenames look like:
1) Do we need the prefix token? (e.g. 43078fa7-81af-46dd-a568-bea275184928)
2) Why is the postfix number appended like this?:
<TABLENAME>1
<TABLENAME>12
<TABLENAME>123
when it could be like this?:
<TABLENAME>1
<TABLENAME>2
<TABLENAME>3
For many changes, as you can see in the above example, there are a lot of seemingly unnecessary numbers added:
Thanks,
Matt
I'm trying to generate a report that includes data, but it errors because the temporary binary files are too long:
Here's my command:Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Code: Select all
<Directory tree> /datacompare /compfile: <Filename>.dcomp /report: <Directory tree>\<Filename>.xls /incdata:yes /reportformat:XLS
And here's what the auto-generated filenames look like:
Questions43078fa7-81af-46dd-a568-bea275184928QUERY_<TABLENAME>1234567891011121314151617181920212223242526272829303132.$$$
1) Do we need the prefix token? (e.g. 43078fa7-81af-46dd-a568-bea275184928)
2) Why is the postfix number appended like this?:
<TABLENAME>1
<TABLENAME>12
<TABLENAME>123
when it could be like this?:
<TABLENAME>1
<TABLENAME>2
<TABLENAME>3
For many changes, as you can see in the above example, there are a lot of seemingly unnecessary numbers added:
could become:<TABLENAME>1234567891011121314151617181920212223242526272829303132
3) Is there a workaround?, as this is currently stopping us from doing a full report with data<TABLENAME>32
Thanks,
Matt