Jump to content

Joost Miltenburg

Members
  • Content count

    147
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Joost Miltenburg

  • Rank
    member
  • Birthday 06/16/1974

Profile Information

  • Gender
    Male
  • Location
    Utrecht

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    10.13
  1. Converting FMP5 to 16

    Be sure to check for unique occurrence names across the solution.
  2. better way to go through data

    In my original post I mentioned that an insert from URL and then parsing the whole thing takes about 4 minutes on the client. Importing with xml/xsl takes me about 5 seconds to get the exact same result
  3. better way to go through data

    So, a little update. I created the xsl in about 10 minutes, but that is skill. Now for the import via import records, type xml using the xsl. The import took about 5 seconds for a slightly larger data set. So JSON with parsing vs importing with xml/xsl isn't in the same ballpark. I would even go so far as to call it a different game.
  4. better way to go through data

    I agree with comment here. I spent a bit of time learning xml in the FM6 days. Thank you Beverly! Some of these new webservices just do JSON. JSON may be maturing, but xml, with stuff like XSD and all the other stuff is pretty useful. Not to mention, xml is pretty well human readable.
  5. 0x0 - illegal xml character

    Your example works, which is nice. When I get an error in my exports, I'll be back.
  6. better way to go through data

    Both tools can be useful in this case. XML/XSLT is going to be my choice for this case. Importing with xslt seems faster than parsing and populating record after record and field after field.
  7. better way to go through data

    Thnx Wim, But I am proficient enough with xslt to tackle this and the client isn't on FM16 yet. Also, I have yet to see a convincing JSON Demo on this, but if you could point me to one...
  8. better way to go through data

    Thnx ! I can check... Exporting to a return seperated list could be intresting. I'll try that! Probably some JSON object would be possible, maybe xml, but no xml-result, but I could do that myself via xslt.
  9. better way to go through data

    LS, There must be a better way to go through the data I receive from a webpage. It returns a list of comma separated emailaddresses about 33k.Currently I am doing it like this.( See below). It takes about 4 minutes. I can move it to FMServer. On FMServer it takes 2:20 for 32114 records. So I'll stick to the server. I using FM15 at this client. Also multiple plugins are available to me, like MonkeyBread 7.3 Kind regards, ---- Freeze Window Delete All Records [ With dialog: Off ] New Record/Request Set Variable [ $i ; Value: 0 ] Insert from URL [ Select ; With dialog: On ; tester::g_text_field ; "url left out for privacy issues.php" ] Set Variable [ $emailAddresses ; Value: Substitute ( tester::g_text_field ; "," ; "¶" ) ] Set Variable [ $emailAdressesCount ; Value: ValueCount ( $emailAddresses ) ] Set Field [ tester::g_text_field ; "" ] Set Variable [ $tsStart ; Value: Get (CurrentTimestamp) ] Loop Set Variable [ $i ; Value: GetAsNumber ($i) + 1 ] Set Field [ tester::emailaddress ; GetValue ($emailAddresses; GetAsNumber ( $i )) ] Exit Loop If [ GetAsNumber ($i)>GetAsNumber ($emailAdressesCount) ] New Record/Request End Loop Set Variable [ $tsEnd ; Value: Get (CurrentTimestamp) ] Set Variable [ $$duration ; Value: $tsEnd - $tsStart ]
  10. 0x0 - illegal xml character

    If I get an error again, I will create an example. I can, quite reliably say, that having the 00x0-character crashes my export. These characters were copy/pasted into fields. Origin: unknown ( but probably Outlook. In the mean time, I have created a substitute function that strips out characters that came up in this link: http://ascii-table.com/control-chars.php. Haven't had the error, since.
  11. Can't upload new solution to server

    Worked!
  12. 0x0 - illegal xml character

    Simply put: every time I find a new character that crashes the export. I track it down and add it you my set field ( theField ; substitute( theField ; theChar ; "" ) before running the export.
  13. 0x0 - illegal xml character

    Using the check box for formatting does not fix the problem. The problem occurs once in a while ; I add the character and that's another one down.
  14. Can't upload new solution to server

    I have the same problem as well. I am using FMS15. I used to be able to upload the files using the client. Currently, I move the files to FMServer manually and then change the file rights to read/write. It is a bit tedious, but a fix for this problem would be nice.
  15. Server SMTP with gmail

    Hi all, It seems that the entered smtp settings are working ; it is just the test-smtp button that seems to be failing. Thanks for all your efforts !
×

Important Information

By using this site, you agree to our Terms of Use.