Jump to content

tomp

Members
  • Content Count

    311
  • Joined

  • Last visited

  • Days Won

    1

tomp last won the day on February 12 2013

tomp had the most liked content!

Community Reputation

0 Neutral

About tomp

  • Rank
    member
  • Birthday 05/20/1947

Profile Information

  • Gender
    Male

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    15 Advanced

Platform Environment

  • OS Platform
    X-Platform
  • OS Version
    high sierra, win 7
  1. tomp

    parsing error on XML import

    I integrated this into my applications and deployed them. Again, I have no idea what the issue was that caused this procedure to stop working, but the case is now closed! Thanks again to 'Comment' for all the attention and help.
  2. tomp

    parsing error on XML import

    Well, that does it. Using your code I finally got the import without the parsing error. With kid gloves I'm going to integrate this script, or if I have to, this file, into my applications. I have no idea what's different here from the way I was doing it in my applications, but at this point I'm not going to lose any more sleep! Thanks for sticking with me and promptly replying to my notes! I'll add a note when I've got it deployed
  3. tomp

    parsing error on XML import

    It's not intermittent. It started about a month ago and has continued ever since. I have 2 different applications deployed (via runtimes) and all my users (that I have heard from) are experiencing the issue Did you import from the file on my web-site without incident? I did some more testing using the xml example files from the Filemaker support/downloads site. I ran a test on my computer, using the attribute import as supplied. All was ok. I ftp'ed the xml file - mdso_attrib.xml - to my web-site, modified the import records script step for the http option, and got the same parsing error experienced with my software. I downloaded the xml file back to the examples folder, took the import records script step back to its original state and tested. All was OK Since the xml file continued to work after the upload/download sequence, it doesn't appear the ftp modified the file. Since my users in both mac and windows environments (they pull the file from my web-site to see if there is an update available for my system) are all experiencing the parsing error I have been describing, I'm concluding the following: 1- if you were able to import using the xml file on my web-site, the problem is not on the web-site. 2- If you were not, perhaps the issue in some way or manner is on the web-site (please confirm whether you used the file on my web-site) 3- Since both my applications and the Filemaker xml example application experience the same issue, the problem is not in my application but lies elsewhere. 4- Maybe in my FM15 installation? Except I have the issue both from the mac and the windows sides. What really has me scratching my head is why this process that has reliably given my users a way to check for a new release of my software for years and years suddenly stopped working.
  4. tomp

    parsing error on XML import

    I apologize for missing your October 15 post. I still have the problem. The style sheet (RM5currentRelease.xslt) has been uploaded for reference here. I have compared it to and it matches the style sheet available from the 'Technical Resources', XML example files, on the Filemaker support/downloads screen This style sheet and procedure for retrieving the data from the xml data source on my web-site has been functioning literally for more than a decade but for some reason has recently ceased to function. I have been using BBedit to update the XML file on my computer and then uploading the new version to my web-site. It hasn't been an issue before. Again, when I use the 'file' option to import the file from my computer using this style sheet, I do not get the error. Only when, after uploading the same xml file to my web-site and using the 'http request' option in the import records script step, do I get the above error. This is the 'http request' source that gives the 718 parsing error for the Import Records script step: http://www.tcpms.com/RM5currentRelease.xml Here's the import script step: RM5currentRelease.xslt
  5. tomp

    BE_SMTP_Send with attachment

    Got it! Thanks for the tip
  6. BE_SMTP_Send is successful when I 'send' an email message without an attachment. The same Send, when adding a single attachment using the file path to a pdf attachment fails with an error code '2' (don't know what that means). The file path that is used is obtained from an 'insert file' script step. I've tried using the file path in both a container and a text field. I've tried both file: and filemac: formats for the file path. What am I missing?
  7. tomp

    parsing error on XML import

    The attached XML file works fine as a 'file' import. But when importing via http (using the same XSLT file), the import gets a parsing error. The xml file and the parsing error description are attached. What's different when importing via http vs. a file import? Where/what is the expected 'white space' when doing the http import? RM5currentRelease.xml
  8. I have been using 'PackageMaker' in macOS for distributing my FileMaker runtime solutions since macOS X was deployed years ago. PackageMaker is 32 bit and will not run on macOS Mojave when it is released. Mojave is likely to be 64 bit only. What is a 64 bit replacement for building distribution 'packages'?
  9. Without the optional HTML and attachment parameters, my BE_SMTPServer/BE_SMTP_Send function calls successfully send an email. When adding the optional HTML and attachment parameters (HTML is null, attachment is text), the email fails with a returned error code 2: CURLE_FAILED_INIT (2) Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental couldn't get done at init time. The attachment has just been browsed for and 'inserted' into a container field, and the file reference for the attachment established via 'getastext(<containerField>' This is the function call in the script that results in the error code of 2: BE_SMTP_Send ( parameters::smtpReplyToAddress; parameters::text3; parameters::text2; parameters::text1; ""; $bcc; parameters::smtpReplyToAddress; ""; parameters::newsletterAttachmentText ) This is the function call that successfully sends an email: BE_SMTP_Send ( parameters::smtpReplyToAddress; parameters::text3; parameters::text2; parameters::text1; ""; $bcc; parameters::smtpReplyToAddress ) Can anybody help with what BE_SMTP_Send is objecting to when including the attachment parameter?
  10. tomp

    deploying FM apps

    I probably didn't make myself clear. I deploy FM runtimes for FM applications that I developed for mom-and-pop businesses in a niche market. I have been using 'packagemaker' for deployment for years, but have learned that Aple does not currently have, nor do they plan to have, a 64-bit 'packagemaker' available when support for 32 bit apps end on OSX. Mike Duncan said: "I use this one: http://s.sudre.free.fr/Software/Iceberg.html" Is iceberg a 64-bit application? Or would I have the sam issue with it (the 'post date' for the link is 6/22/15). Don't want to invest a lot of 'learn' time if it doesn't resolve my issue.
  11. tomp

    deploying FM apps

    What installers are people using to deploy their FM apps on Macs? OSX Packagemaker is 32 bit and soon won't be supported.
  12. tomp

    splash screen shows in Runtimes

    Thank you. That did it. Had no idea how that worked. I noticed that my QBO Connector Plugin was already in the 16.0 Extensions folder. Guess that went there automatically when it was installed. Thanks again. Mission accomplished!
  13. I have un-checked FM Books Connector in preferences/plugins for all installed FM versions, yet when I create runtimes, the splash screen shows every time the app is run. I don't think my clients see it, but it wastes 30 seconds of my time every time I run the apps. These apps do not use FM Books Connecter. Since I've un-checked the plugin in preferences for all my installed FM versions, what else do I have to do to suppress the splash screen in the runtimes (it doesn't show when running FM Pro or FM Pro Advanced)?
  14. We are having an issue with the ipad occasionally getting a 'host not found'. The 'external data sources' have the proper IP address of the host computer, but even with the ipad right next to it, the 'host not found' message occurs. Is there a way to make a hard connection between the ipad and the host for filemaker-sharing?
  15. It is seen with the other list of files that came with GO (assets, contacts, etc.) When it is clicked, the cursor just begins spinning (I assume meaning FM Go is not responding) and never stops. We have deleted and reloaded FM GO and reloaded the app file to the ipad without resolving the issue.
×

Important Information

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