I'm only peripherally familiar with ASP.NET (I let others here handle that), but if there's a way to set up a web service on your existing app that accepts a POST request, you could use that capability to post the new data into the .NET app from Go. Version 13 has an HTTP POST option in the Insert from URL script step that can process such requests.
Others here may have a better idea.
Thanks Mike, yes I could easily create a web service to expose the data.
That would take care of the fetching of the data but I dont think im in luck when trying to get it back.
I dont think there is a way to post the data back to the web service? Hope im wrong..
Can't say. Like I said, not my area. But that would be something I'd research; it would be a really good way to get the data back to the .NET app without having to jump through a lot of hoops.
Is there a way to program a simple ASP page that accepts a POST request with appropriate parameters that just parses the data and then submits it to the database? I know you can do that with PHP.
Yip, I can easily create a web page or service to grab the data but I cant see a way of exporting to this URL from filemaker go.
If I had a url
I cant see how to push data to it from filemaker but hopefully someone will have accomplished this.
yes that gets data into filemaker, i can handle that ok, its getting data FROM filemaker into the back end where I need help.
Read the link I posted and investigate the httppost option.
Another option is to use a web viewer that points to your web page and embed the necessary parameters in the URL.
Thanks, yes the httppost is great for importing, as for exporting then yes that could be a plan indeed to use the webviewer to navigate to my web service. thanks again..
I am in agreement with Mike M:
I believe that the httppost functionality should be sufficient to provide for both your data import and export needs.
The only reasons that I can currently imagine such that this might not work out would be:
- The webservice that you set up requires one or more http post headers which can not be set in the httppost IFU script step
- Security of the transmission warrants using https, including verifying the server's identity
If you are up against either of the above two points, you might take a look at an attempt I made to work around these issues using a webviewer:
AFAIK, no one has used the code that I posted in any production setting, but you are welcome to take the code and use it, improve it, build upon it, etc.
To reiterate my first comment:
If you are not running into either of the two issues I mentioned, I think you'd be better off using IFU, as Mike has proposed.
HTH & best,
im absolutely NOT against the httppost but I initially thought it was only to import records but I need to investigate it further, I have some documents now that I will read through and test this out, thankyou both for your time.
Ill admit id prefer to take FM server out of the equation
You really can't.
If the data needs to end up in FM then you need FMS to be your central hub to accept the data in any of the supported standards.
FMP and FMPA can act as hosts of some sort but they have very clear limitations. If you are familiar with .NET server-side scrpting you could see what fmdotnet.org offers you to work with live FM data.