Steve Wright Posted September 30, 2004 Share Posted September 30, 2004 I apologize if this seems silly. I have a situation whereby a client is entering information into our fmp6 databases via a cdml web page. However, they do have their own fmp6 databases and are currently having to rekey or paste the information into theirs as well as our web page. Rather than go through all the complications of linking theirs with ours what seems to be the alternative is for the client to be able to export out the data to their desktop using the web browser. I know this probably means xml. I think i know the theory but am a little vague on the nuts and bolts. Can anyone give me any practical advive. Or has anyone actually done this. Link to comment Share on other sites More sharing options...
Garry Claridge Posted September 30, 2004 Share Posted September 30, 2004 Is the data originating from the Client's database? Is the data, being entered into your database, creating a new record or editing an existing record? How much data is being entered? Is the Client using FM6? If so, they may also be able to use CDML to populate the Form. A number of possibilities exist. One may be to use a Script with the "Open URL" step. Another may be to use Applescript and Javascript. All the best. Garry Link to comment Share on other sites More sharing options...
Steve Wright Posted September 30, 2004 Author Share Posted September 30, 2004 No the data is originating from our side, although the client needs to update their data in their own filemaker pro 6 database with some of the information in ours. The amount of data is very small by many standards. A few hundred records (text only) at most. THe problem is that we are not the only company that provides the client with similar data so we cannot persuade them to use our system in its entirety. thanks for your help Garry. Link to comment Share on other sites More sharing options...
Jeff Spall Posted September 30, 2004 Share Posted September 30, 2004 Hi, if your web database doesn't have really heavy traffic, then you can run an export script through the web interface. Have a field which flags exported yes or no and then just do a find on that through the web page, running a script which does the export into a set folder. (see the attached file for a page we have that does just that - In this example there are eleven possible export files. You need to change the extension of the file from "txt" to HTML - can't upload an html page!) On your other database, you can run an import script every now and then (or have an (Applescript app. running on that machine which calls the import script every so often), or, if you wanted to get really tricky, have one DB email the other to trigger the script. The export script has worked very reliably for me on a database that only got a few dozen users per day, although it was on a FMPro server that was getting maybe 75000 hits per day. The script is very fast, so it seems to avoid the usual script pitfalls and it's very simple, too. regards, jeff activerecords.txt Link to comment Share on other sites More sharing options...
Jeff Spall Posted September 30, 2004 Share Posted September 30, 2004 Post deleted by Jeff Spall Link to comment Share on other sites More sharing options...
Steve Wright Posted October 1, 2004 Author Share Posted October 1, 2004 thank you to jeff and garry for spending some time on this. it has given me some ideas. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 7239 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now