Q: What versions of Java are supported?
A: Our products are tested and supported on Java JDK/SDK 1.6.
Q: How do I report bugs?
A: Each project has its own bug tracking system. These bug
databases are open to the public and anyone can go and report
issues with our products. To obtain the list of our products
and their respective bug tracking database, please visit the Community home page.
Q: How can I contact the developers of these projects if I
Q: How do I make enhancement requests?
A: SQL Power Developers communicate with the developer
community using Google Groups. You can contact us at the
following Google Groups for each project:
SQL Power Architect Developers:
SQL Power DQguru Developers:
SQL Power Wabit Developers:
Q: How do I use a SQL Power product from behind an HTTP proxy?
A: You can use Java's built in proxy support. To do this, you have to set a few system properties:
How you accomplish this depends on which operating system you're using (Windows, OS X, or some form of Unix).
Please note: for clarity, the following examples refer to SQL Power Wabit, but the instructions will work for all of our apps.
If you are not using SQL Power Wabit, just substitute the name of the app you're using.
On Windows, you can provide additional command-line parameters in a file called appname.l4j.ini.
To do so, follow these steps:
- In Windows Explorer, locate the application's .exe file
(for example, C:Program FilesWabitwabit.exe)
- In the application's folder, create a new text file called wabit.l4j.ini.
An easy way to accomplish this is to right-click on the folder window's background, the select New > Text Document from the popup menu.
Note: if you are using SQL Power Architect, call the file architect.l4j.ini; for DQguru, call the file dqguru.l4j.ini
- Open the newly-created file in Notepad
- Paste the following contents into the file, and edit the settings as necessary for your environment:
# SQL Power Wabit runtime configuration
- Save the file, then relaunch Wabit.
Mac OS X
On Mac, you will need to edit the application's info.plist file. To do so, follow these steps:
- In the Finder, locate the application's icon
(for example, /Applications/SQL Power Wabit.app.)
- While holding down the Ctrl key, click the application's icon.
- Select "Show Package Contents" from the popup menu. A new finder window will appear.
- In the new finder window, open the Contents folder.
- Open the Info.plist file in TextEdit.
(Once TextEdit is running, you can do this by dragging the Info.plist file onto the TextEdit icon in the dock.)
- Locate the following lines near the bottom of the file:
- Change them to:
- Save the file and re-launch the application.
Linux and other Unix-like Platforms
If you are using the Unix distribution, simply include the appropriate command-line parameters when launching the application. For example:
prompt% java -Xmx600m -Dhttp.proxyHost=myproxyserver.com -Dhttp.proxyPort=80 -jar wabit.jar
Q: How do Parameters work in SQL Power Wabit?
Note that as of SQL Power Wabit version 1.3.4,
Parameters are still experimental and only recommended for advanced users.
A: There are two places where you can use parameters: in a report,
and in a where clause on a query.
1. Report Parameters
To create a report parameter:
- Click on the + button in the lower right parameters panel.
- You can create a date picker, a text field or a drop down list.
2. Query Parameters
Once you have parameters defined in a report, you can also use them in a query.
- On a report, once a table is in the play pen, select the where field beside a column,
then hold "ctrl" and press the space bar.
This brings up a Parameters window which allows you to
select a field out of the project as a parameter.
- Select the variable using the "..." box in the top right.
The box will display a menu of all objects in the tree.
Hovering over one will display all possible parameters
in that object that can be used as a variable,
including titles of objects and Java preferences for Wabit.
- Once a variable is selected, you can define a default value.
- Note that once you press "Insert" to add the variable, you can't return
to the editor for the parameter. (To change the parameter at this point, you would
have to delete all of the inserts and make a new parameter.)