Showing posts with label mySQL. Show all posts
Showing posts with label mySQL. Show all posts

Thursday, January 10, 2008

dbQwikEdit SQL Tool Prices Slashed

dbQwikEdit, TheDevShop's multi-database data manager has just gotten cheaper with Pro version selling for only $39.95 USD. That's an incredible price, the competition can't even come close, neither in price or functionality. I did a quick survey on the Internet, most competing products are priced between $69 to $250 USD. That makes dbQwikEdit the best value in town.

For those who are not familiar with dbQwikEdit, it is an SQL tool and visual query builder. It works with most databases so you don't need to buy and learn a different took for every database you use. Like all the dbQwik family of tools, dbQwikEdit does not require that you have advanced programming and technical knowledge to use the tool productively. But if you happen to be a database SQL guru, the tool has no problems supporting the demands of power users.

You can find more information and a free trial edition on the web http://www.dbqwikedit.com/

Monday, August 27, 2007

dbQwikMySSH 1.0.0.4 - Painless MyODBC SSH Management

We just introduced dbQwikMySSH only a few short weeks ago and it is doing very well. This week we released a minor update to make it even easier to use. We added a new function to automatically reconfigure your MyODBC connections to pass through the secure SSH tunnel. Restoring them is just as easy. You simple right click the connection to secure, and choose the Secure option in the popup menu. To restore connections to their original settings you right click a secured connection and choose the Restore option.

There are a couple of other tweaks to the interface to make it easier to understand what’s going on. For instance the MySQL server detection is easy to confuse with your connection settings. The Server check is just to see if there is a MySQL server listening; it does not have anything to do with the authentication of your MySQL connection. So we have refined the interface a bit to try to make that a bit clearer. A couple of small bug fixes are included to round out this release. If you are installed and want to get the latest, you can run the live-update. Otherwise just download the latest install from:
http://www.thedevshoponline.com/dbqwikssh.html it has the latest updates.

Wednesday, August 08, 2007

dbQwik™MySQL2Access v 1.0 – Moves MySQL to MS Access.

This week we introduce a brand new member to the dbQwik™ family of products. dbQwik™ MySQL2Access is a program that moves MySQL databases into MS Access. It can either connect directly to MySQL or it can read in MySQL dump files. The program can either create new MS Access Databases or import into an existing MS Access Database. You can selectively import tables.

The program is very simple to use. Enter your MySQL login details or browse to a MySQL Dump File. The tables are listed, and you just pick the tables to import and all rest is done for you.

This program is great for creating local copies of local or remote MySQL databases. Local copies can be used as back ups, or “off-line” copies for reporting and anlysis. The advantage of MS Access is that it is highly portable and integrated into MS Office. There is no need to install MySQL in end users PCs. This is a handy little utility that you can use again and again if you have data in MySQL.

dbQwik™MySQL2Access is available for download from our software store: www.TheDevShopOnline.com. There is a free trial version. The trial has an import limit of 25 records per table. You can buy the full version for only $19.95.

Wednesday, August 01, 2007

dbQwik™MySSH v 1.0 – Debut of Secure MySQL SSH connection.

This week we introduce a brand new member to the dbQwik™ family of products. dbQwik™MySSH is a SSH client, highly specialized for working with your MySQL connections. What is SSH? SSH is a secure encrypted protocol for internet communications. Using dbQwik™ MySSH, ensures that all data exchanged between your PC and your MySQL host remains private and protected from eavesdropping hackers. There is another advantage to using dbQwik™MySSH, that is being able to connect to remote MySQL servers even when these servers block the standard remote connection on port 3306. If your hosting allows SSH connections, you can use dbQwik™ SSH to connect, and dbQwik™MySSH will proxy all your MySQL traffic through its secure connection.

What makes dbQwik™MySSH different than other SSH clients? Most SSH clients are general purpose utilities that require that you learn and understand how to set it up and configure it using cryptic commands. dbQwik™MySSH is highly specialized to work with MySQL and MyODBC. It provides a beautiful graphic interface that allows you to instantly see exactly which connections are using SSH and which ones are not. dbQwik™MySSH takes care many of the settings and configuration set up, so you only have a few fields to enter to establish your SSH connection. There simply is no easier way to connect to MySQL using SSH.

dbQwik™MySSH is available for download from our software store: www.TheDevShopOnline.com. There is a free trial version. The trial has a limited connection time. You can buy the full version for only $19.95.

Saturday, July 28, 2007

dbQwikEdit 3.3.0.2 Expands Database Support and Fixes

We just released dbQwikEdit 3.3.0.2. In this release many of the functions of the program have been enhanced to cover a wider variety of databases, particularly desktop databases such as Dbase and Paradox but some additional Oracle work is also in this release. We also fixed a bug that caused the program to seemingly hang if you allow it to auto adjust your myODBC settings. Now the auto-optimize of myODBC settings works better. Optimizing your ODBC settings will address the dropping of MySQL connections resulting in “MySQL server has gone away” errors.

We have tweaked the query syntax builder to better size the list boxes on start up and done a lot of work on the batch move. You can now create target table definitions from queries as well as tables. Parameterized queries now process better.

All an all this is a pretty limited release as far as new features, but it adds a ton of stability and is worth the live update.

Friday, June 15, 2007

dbQwikReport 1.3 Vista Ready

Today we release dbQwikReport version 1.3. It is a both an important release, and a boring release. It is important in that, it is now compatible with windows Vista, and boring in that there no great new features for me to write about.

Anyone already using Windows Vista, or planning a move to Vista, can rest assured that their investment in dbQwik products is a sound one. dbQwikSite, dbQwikReport and dbQwikEdit all will run on your Vista machine. Only one left to migrate: dbQwikSync Pro and you should expect that one shortly.

There is one significant enhancement in dbQwikReport 1.3. It is a bug fix, of sorts. Actually the bug is with Microsoft ADO, it simply will not handle MySQL Timestamp data types. So, our fix is that we catch the error, and we allow you to continue designing, but without any data in your preview. When you deploy to PHP/MySQL all your data will appear. There are a couple important things to note here. It is far better to use DateTime data types in MySQL if you want your tables to be accessible by any tools that are based on MS ADO, technology (like the dbQwik Products and ASP). The resulting data storage is the same. Users of dbQwikSite should note that we have not fixed this issue yet in dbQwikSite… so best to avoid Timestamps in MySQL all together.

dbQwikReport 1.3 is a free upgrade available via live update. You access live update from the help menu of the program.

While we are on the topic of technical “stuff” and version numbers there is an important tidbit I have to share with you. I was using dbQwikEdit on my laptop lately. I could not believe how unstable it was; no matter what I did it seemed to go wrong. After firmly scolding all the developers with harsh words about quality and the likes, I was asked the question:
“What database?”
“MySQL, and we are supposed to support it! Nothing new here folks!” I retorted.
“What version of myODBC are you using?”
“I just updated maybe a couple weeks ago, 3.51.14.0” was my reply as my confidence began to fade.
“Can you try 3.51.15.0?”

I returned to my desk, and about 2 minutes, later I was both humbled and happy. It was like dbQwikEdit had magically transformed from a “clunker” to a “cool tool”. I learned two things: 1) go easy on the staff and 2) make sure that my ODBC drivers are stable. I share this with you in case anyone out there is using myODBC 3.51.14.0. and thinking: hey, the TheDevShop software doesn’t work at all. Please, please upgrade your myODBC to 3.51.15! It will make a major difference and bring serenity to your query building.