Do you think writing embedded SQL code for RPG is more complex and time-consuming than it should be? You're not alone!

By Scott Salisbury

Have you ever started down the path to creating an SQLRPGLE program only to turn back and do it the old-fashioned way? If you said yes, I'll bet it's because RPG CHAIN, SETLL, READE, etc. are easier and less hassle than trying to unscramble the proper use of statements, prepared statements, host variables, return codes, and all the rest.

Coding SQL within RPG can be tedious, but what if you could automatically generate SQL for RPG, SQL for Java, and SQL for PHP in a just few clicks?

by Scott Salisbury

Have you ever avoided using SQL in your RPG programs because embedded SQL is a hassle and it's just easier to do it the old-fashioned way? Have you ever wished your RPG programs could access data from Microsoft SQL Server or Oracle? Do you work with multiple databases and multiple SQL client tools? What about Java and PHP? Both use embedded SQL. Are you using them yet?

SQL(snap) simplifies SQL tasks and turns hours into a few clicks.