OliverA Expert Licensed User Longtime User Sep 18, 2017 #1 On a Sunday, if I tell someone I'll have a program ready sometime during the week, I'll probably be lucky to have something up and running by the first day of the next week. But @@Erel? No, his definition of sometime during the week means the same day! Actually, less then 12 hours. How is someone supposed to compete!!! Less than 12 hours later:
On a Sunday, if I tell someone I'll have a program ready sometime during the week, I'll probably be lucky to have something up and running by the first day of the next week. But @@Erel? No, his definition of sometime during the week means the same day! Actually, less then 12 hours. How is someone supposed to compete!!! Less than 12 hours later:
Erel B4X founder Staff member Licensed User Longtime User Sep 18, 2017 #2 Overall it was simple library to make. JdbcSQL.jar is the same file as jSQL.jar. The only changes required were in the XML file. There are two important identifiers: the short name (read from the XML file) and the full name. The full name includes the package name which in the case of jSQL is anywheresoftware.b4j.objects.SQL. This allowed me to reuse the same jar without recompiling or modifying the source.
Overall it was simple library to make. JdbcSQL.jar is the same file as jSQL.jar. The only changes required were in the XML file. There are two important identifiers: the short name (read from the XML file) and the full name. The full name includes the package name which in the case of jSQL is anywheresoftware.b4j.objects.SQL. This allowed me to reuse the same jar without recompiling or modifying the source.
