In Part 1 (PBDJ, Vol. 9, issue 2) I provided the information necessary to
build EAServer components. I also introduced the development work flow, a set
of steps to build an application using EAServer components. Using the
workflow, you can create either a Web-based or a client/server application.
Armed with this knowledge, you’re now ready to create EAServer components.
This article focuses on building components using the workflow as a guide.
Given this, it might be useful to have Part I handy so you can refer to the
workflow as necessary.
Developing EAServer Components
Assuming that you’ve thought out each object and determined those that
belong in EAServer, begin your server-side development by creating a
directory structure to house your components.
This directory structure should be duplicated on all development machines as
well as on a machine all developers ca... (more)
Recently, my development team was asked to modify our inventory management
application to use Microsoft SQL Server (MSSQL) as its back-end database
instead of Sybase's SQL Anywhere (ASA).
At first we thought the task wouldn't be difficult because MSSQL was
originally a Sybase product (Sybase SQL Server, the predecessor to Adaptive
Server Enterprise) and the iAnywhere engineers had been working diligently to
make ASA compatible with Sybase's Adaptive Server Enterprise (ASE). We found
out just how wrong we were in very short order.
There are a number of differences between the two ... (more)
Recently, my development team was asked to modify our inventory management
application to use Microsoft SQL Server (MSSQL) as its back-end database
instead of Sybase's SQL Anywhere (ASA).
At first we thought the task wouldn't be difficult because MSSQL was
originally a Sybase product (Sybase SQL Server, the predecessor to Adaptive
Server Enterprise) and the iAnywhere engineers had been working diligently to
make ASA compatible with Sybase's Adaptive Server Enterprise (ASE). We found
out just how wrong we were in very short order.
There are a number of differences between the two ... (more)
Timothy P. Beck, former managing partner and founder of IntelliServe LLC (a Sybase Consulting Partner, an iAnywhere Systems Integrator, and a Sybase Education Agent) is now a principal developer for JDS Solutions Corporation in Carlsbad, California. He has been working with PowerBuilder since 1991, has been a certified instructor of Sybase technology for more than ten years, and has personally assisted dozens of customers in developing client/server and Web applications using Sybase’s EAServer.
David Lucas
Shaul Efraim
Terence Martin Breslin
Cory Marchand
David Hughes
James Carlini
John Iffert
Dan Stolts
Joe Zeto
