W
wood
Guest
First, I would recommend the OpenEdge Service objects rather than the direct database connection if you plan continue updating the database via ABL (even ChUI) while accessing it from Rollbase (effectively via SQL), so that all the business logic can be encapsulated. There is no specific reference to multiple clients (ABL and Rollbase) accessing the same database in Rollbase In Action because this is just 'normal' behavior. No matter which way you go (OpenEdge Service object or External Database Tables) you can have multiple clients and client types reading and writing data. Ultimately it is just the power of the OpenEdge stack which is multi-user. There is nothing special about Rollbase here.... it is just a Java (or SQL) client that can coexist with ABL clients..
Continue reading...
Continue reading...