General discussion fp and sql

[Robert Haussmann]

Haven't used devExpress, but is it able to consume web services?  If so, that might be your best bet.  I guess the question is, what exactly are you trying to accomplish?  Is this solely for reporting or for other applications as well?

Bob

-----Original Message-----
From: Filepro-list [mailto:filepro-list-bounces+haussma=nextdimension.net at lists.celestial.com] On Behalf Of Richard Hane via Filepro-list
Sent: Friday, March 18, 2016 4:47 PM
To: mschw at athenet.net; Filepro List <filepro-list at celestial.com>
Subject: Re: General discussion fp and sql

[sorry top posted]
Thanks for those who responded.
I should have stated that this would be a Windows not *nix appliaction.
I do want to continue to do my processing in fp and not have to relearn the wheel in SQL.  This Production shop mgt and scheduling software has been working fine for over 15 years.  I have no problem working data back and forth with fileProODBC and SQL.  However all that being said I think my best option will be to forego .NET and use either fpWeb for the screens and port the static data to SQL for use with devExpress.
Has anyone ever heard or seen devExpress tie to filePro directly?  That would be the best option.
ThanksRick Hane
 

    On Friday, March 18, 2016 2:54 PM, Mike Schwartz via Filepro-list <filepro-list at lists.celestial.com> wrote:
 

 > I know this might sound crazy but is anyone using SQL tables as a front end
> on filePro?  I like the use of .Net screens and report writers like 
> devExpress

> Thank you in advance, Rick Hane, Yore Software Company

    One way to read and write web data to filePro from .NET (or other) web applications is by configuring Apache Tomcat or something similar on your Unix (or Windows) server. 

    By using Tomcat, you are entirely using filePro processing tables to pass data to and from the filePro files and into your web applications.

    The advantage of working entirely within filePro is that all the filePro indexes will stay properly updated and filePro data entry and posting rules will be obeyed.

    The filepro processing called by Tomcat can be a little tedious to write.  It has to be able to handle a lot of bad calls from the web app.  For example, if a .NET developer requests info using an invoice number that does not exist, you have to make sure your code returns a message, something like, "That invoice number does not exist..."  

      You can pull large chunks of data back through Tomcat in order to populate SQL tables; preferably read-only SQL tables.  For example, your web designer could send a tomcat request for all the invoice numbers and a little data from each invoice and then populate a temporary SQL table with it.  You probably wouldn't want to pull back all the fully populated invoices for one customer and then try to load several SQL tables with the resulting data, because that would take several seconds (or minutes) to build in filePro, then transmit back and load into SQL files.  

Mike Schwartz


  

 


_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes http://mailman.celestial.com/mailman/listinfo/filepro-list


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20160318/2f0aef23/attachment.html>
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes http://mailman.celestial.com/mailman/listinfo/filepro-list