In a previous post (B4J Connection to Database Example…) I demonstrated through a very simple application how to connect within a B4J application to a SAP SQL Anywhere Database. It’s not always easy to find how we can connect to a database. This is because, when connecting to a database using JDBC, we have to know which driver we will use and also the required JDBC URL to communicate with the database server. This information isn’t always easy to find, as they are different versions of clients, and each database client may have different driver & settings!
As mentioned in the title, this time I will give an example of a connection to a SAP ASE Database. Currently, I will be testing the connectivity to versions 15.7 and 16.0 of the product. As with any database, the first thing we need to check is that the JDBC driver option of the client was checked and installed during client’s installation (this can be done through control panel add/remove programs option). The second is to copy two files to out Additional Libraries folder (this path is declared in B4J IDE as shown in the following screenshot).
The files needed to be place there are:
In this post we will see a Database Connection example in B4J. The database we will use is SQL Anywhere 16 (Developer Edition). So we need to have installed SQL Anywhere 16 (Developer Edition) to our computer.
First thing we must have in mind is that B4J produces java code. To connect to a database we need to have a JDBC driver. SQL Anywhere does provide a JDBC driver (sajdbc4.jar). To use it in B4J we have to copy the sajdbc4.jar & jodbc4.jar to our additional libraries folder. Those files are provided with SQL Anywhere client installation.
If all steps mentioned before are done, then we are ready to write our first application in B4J to connect and query a SQL Anywhere Database. For the purpose of our example we will use the sample database provided with SQL Anywhere 16. Continue reading
As mentioned in my previous post (A simple batch compressor with autoit using winrar [Part-1]), in DbbupCompressor I use 3 functions. First one is check4Files2Compress. The code is: Continue reading
This is a simple project in autoit. What we want to achieve is to specify someway a folder with a set of subfolders (in this case) and create a compressed file (a .rar file in our case) for each folder. After each folder has been compressed, we also want to delete the folder to free up space.
We use autoit to create an executable (I describe that bellow in detail) and an ini file (configuration file) from were we provide some information to our executable. In my case the exe will be named DbbupCompressor.exe and the ini DbbupCompressor.ini (only the extension will be different). Continue reading
In 2008 Q3 Sybase released the long expected Powerbuilder 11.
What Sybase did with Powerbuilder 11, was magic even if it had many problems and was in a point of view incomplete… This is still my opinion… And at that point, compared to Visual studio they had an advantage. Within pb 11 IDE, we were building an application and afterwards we had the ability to choose the way we wanted to deploy in (win32, winform or webform – ASP.NET)… The result wasn’t the best expected, but if we think that webform deployment was introduced in pb11 and then no changes or improvements have been made to this target, it was a great job. And I really believe that if they had spent some more time to improve deployment to webforms, without thinking about silverlight deployment option (witch by the way they started to work on, and then abandoned due to Microsoft strategic change), and later about HTML5 (witch was finally abandoned), they could keep webforms more up to date! All that belongs to the past. After Sybase acquisition by SAP, they removed webforms target (before that Sybase did also removed com targets in v. 11.5 & v 12) from the product in a maintenance released (v. 12.5.2). I think it was the first maintenance release for the product, were a future was removed without any other change. In the meantime then didn’t have an official roadmap for future releases…. Version 15 which was expected for a very long time was finally released in August 2014 (with some new features and a v. no changed from 15 to 12.6). Since then SAP seemed not to interested in Powerbuilder. In June 2016 they “sold’ the product to Appeon, which has a great interest to see Powerbuilder as they sell Appeon Web and Mobile, which is a tool to port a powerbuilder application to the web and mobile world.
In my previous Blog post (PB 12.6 – What I Expected… What is missing.) I mentioned Support for PB Controls in toolbars. This is a very nice feature (by the way an implementation of that feature exists in PB Ulitmate Suite and also in Advanced Gui Controls sample application which was implemented by some excellent developers). This feature was not delivered, or to be more accurate, was never delivered working…
The concept was to allow the developer to add also other kind of controls to the tollbar, like a dropdownlistbox or even a userobject… Continue reading
This is an old discussion. But I insist because even if PB 12.6 was finally released September 2014, it was a different product from what I expected and surely missed lot of features that some of us expected for PB 15. I will explain my point.
During the past we saw some presentations for PB 15 (most of them right after PB 12.5 was launched). It was a good thing back in 2011 to have some feedback about our preferred IDE future. Something we are still missing today… It was one thing Sybase did well, but unfortunately had not enough time to complete, as the migration to SAP was in progress. Continue reading