Our company is looking for a full-time Delphi developer. The job does require the developer to be onsite. We have development offices in Alpharetta, GA and Cape Coral, FL.
Our company is looking for a full-time Delphi developer. The job does require the developer to be onsite. We have development offices in Alpharetta, GA and Cape Coral, FL.
What the Delphi Application Developer does: 99% of the product is written in Delphi with an MS SQL database tier. The product is an n-tier architecture that is fully internet based. We manage and work with VLDBs in the terabytes. The system is built using numerous components such as Real Thin Client, ReportBuilder, DevExpress and other components. We do have smaller sub-systems in C# and Cognos. We are a small team looking for a self-starter that adapts quickly to a fast paced environment.
What experience we require: Proficient in Delphi and SQL. Knowledge of healthcare billing processes, collections, electronic interfaces, and general accounting principles is advantageous.
Who we are: abeo is a leading, nationwide medical billing company that provides a wide range of services to its clients that include, but are not limited to, billing and A/R management, practice management and billing software. abeo is the employer of choice for client-focused, results-oriented individuals who thrive on challenges and problem solving.
The position offers Medical, Dental, Vision, 401k and other benefits. It is a salaried position with a pay range based on experience.
Contact Jeff Teasdale at jeff.teasdale@abeo.com to apply for the position or to request more information.
What the Delphi Application Developer does: 99% of the product is written in Delphi with an MS SQL database tier. The product is an n-tier architecture that is fully internet based. We manage and work with VLDBs in the terabytes. The system is built using numerous components such as Real Thin Client, ReportBuilder, DevExpress and other components. We do have smaller sub-systems in C# and Cognos. We are a small team looking for a self-starter that adapts quickly to a fast paced environment.
What experience we require: Proficient in Delphi and SQL. Knowledge of healthcare billing processes, collections, electronic interfaces, and general accounting principles is advantageous.
Who we are: abeo is a leading, nationwide medical billing company that provides a wide range of services to its clients that include, but are not limited to, billing and A/R management, practice management and billing software. abeo is the employer of choice for client-focused, results-oriented individuals who thrive on challenges and problem solving.
The position offers Medical, Dental, Vision, 401k and other benefits. It is a salaried position with a pay range based on experience.
Contact Jeff Teasdale at jeff.teasdale@abeo.com to apply for the position or to request more information.
Is sponsorship available
ReplyDeleteI'd like to know if you use an ORM layer between the VLDB and DevExpress components. Just interested, cannot apply for the job.
ReplyDeletePrakash Shirodkar Unfortunately sponsorship is not available.
ReplyDeleteDany Marmur We do not use an ORM. We use DevArt's dbExpress to connect the middle tier applications to SQL Server. The server side calls are mostly hand coded or generated SQL depending on the function. Cognos does use a model but we essentially BCP our data from multiple databases into a single warehouse DB that Cognos ties into. The app was designed in 2000 with Delphi 7 and SQL 2k. It is updated to the latest Delphi and SQL but still has that "old school" feel.
ReplyDeleteCameron Cole, i see. I'm more interested in the last "stpe". Did you "hand code" the requests from the client(s) to the middle tier? I'm asking because DACs provide a lot of notifications that make modern grids and other elaborate controls (DB aware) a lot easier to work with.
ReplyDeleteDany Marmur Essentially the client makes a function call to the middle tier over the internet via Real Thin Client, the middle tier runs a query using dbExpress and sends that query back to the client as a clientdataset. Grids, edit controls, etc are bound to that returned clientdataset. Changes made to that clientdataset can be sent back to the middle tier which automatically produces Insert/Update/Delete statements based on what changed in the clientdataset compared to what was originally sent. We effectively bind everything client side and rely on a differential engine in the middle tier to create automated changes. It is a straight forward process that a decent Delphi developer can pick up in an afternoon.
ReplyDeleteLarge reports and datacubes are requested by a client-to-middle-tier function call. The middle tier then kicks off a process that generates the report in ReportBuilder or cube to a SQLite DB. Once the report/cube process is finished it is added to the users queue and a message is sent to the client. When a user views a report/cube we use SFTP to fetch it as SFTP is a better streaming protocol.
Cameron Cole, thank you! Yes i have been experimenting with such setups. I did not find a "clientdataset" that i deemed good enough for that task yet, though :)
ReplyDeleteDany Marmur Real Thin Client has their own but it is built off of Delphi's TClientDataset. TClientDataset works most of the time but it corrupts easily and is best used with a few properties turned on/off. I would love a light weight TClientDataset alternative but most like KBM are even heavier. TMS used to have one but not sure they do any longer.
ReplyDeleteCameron Cole, maybe we should start another thread :) I threw out TClientDataSet by the reasons you mention. I have used KbmMemTable in other situations and agree with you about it too (i had a lot of headaches with updates at that time, years ago though). I started some (rather extensive) trials with TeeBI and initiated a conversation with the vendor. It looked good in the beginning but the vendor lost interest at the point where i came up with plans to append metadata to the delta and TDataSet compliance was still buggy.I think the product went in another direction eventually. So last year that is where i left my research into all this. I use RTC too (but not for this kind of remoting). Still looking...
ReplyDelete