Office politics

[Walter Vaughan]

Fairlight wrote:
> Sounds familiar.  A client of an fP developer client of mine wanted to take
> his fP-based business on the web for online orders and commerce.

[snip]

> A -year and a half-
> later, he had a redesigned web site, alright. [snip]
 > But now he has a nice ASP (blech!) based
> site that doesn't do any more than it already had.

No, No, No. The problem is not that they used ASP, or PHP, or Python, or 
whatever.

The "PROBLEM"(tm) is that we still do not have database independence in 
our rapid application development tool.

The "lite" version of filepro should use native key, data, and indexes.
The "Enterprise" version of filepro should be able to use Oracle, 
Sybase, Interbase, PostgreSQL, MySQL, Xbase, MS-SQL, DB2, SQLBase, 
Ingress, whatever.

Those are the blinders that makes my job more difficult every day.

fpOBDC is a good start, but until there is an uncoupling of the rapid 
application toolset and the current database structure for *nix based 
filePro, we're always going to have to justify why we still are 
developing in filePro.

Who cares if they wrote it in ASP. Let 'em write in whatever you detest
<%@ Language=VBScript %>
<% Set Conn = Server.CreateObject("ADODB.Connection") %>

As long as you can see the data clearly from a filePro perspective, and 
generate reports and update records as needed, I don't care.

--
Walter 'tired of tradeoffs' Vaughan