nynaevelan wrote:I assume when you add the Option sheets you will include an option to suppress the tables for the values that do not have any tracks to meet the criteria?
ZvezdanD wrote:nynaevelan wrote:I assume when you add the Option sheets you will include an option to suppress the tables for the values that do not have any tracks to meet the criteria?
There is a new update: v1.2 - 2009-04-12
- Added: Options Sheet and Options dialog with options for display of sections in the report.
Mizery_Made wrote:Now that you have implemented the ability to exclude certain parts, does this simply hide these sections, or does it also prevent the SQLs running that would fill these sections if selected?
The suggestion is that since you've now got an options sheet, maybe "Top #" is an option that should be moved from the script itself, and into this new option sheet?
The window has the option to Maximize, however if you do, it covers the entire screen. That includes the task bar, which isn't usual behavior for Windows. Any way to get it to only cover the "Application Area" (a.k.a., the entire screen, except where the Taskbar is) when Maximized? Maybe this is an MM bug, since I semi-recall Bex's SQLViewer doing the same.
nynaevelan wrote:I always get this error when selecting a particular filter from the drop down box.
nynaevelan wrote:On the db you have it is Editing - Library Editing but on mine I renamed it Primary - Library Editing.
ZvezdanD wrote:nynaevelan wrote:On the db you have it is Editing - Library Editing but on mine I renamed it Primary - Library Editing.
There is a new revision. Thank you very much for the report.
Mizery_Made wrote:Make more sense this time?
Mizery_Made wrote:The script doesn't play too nicely when a Filter Name contains an apostrophe. Tried running it on a filter I have named "TI -- Albums With -- Only --Albums--'s" and it gave me an error, something about ": near s" or something, which seems to point to the apostrophe. I renamed the filter and removed it, and it ran fine. Seems it needs to be escaped or something in the SQL query or something.
Users browsing this forum: No registered users and 6 guests