Jump to content


  • Posts

  • Joined

  • Last visited

hermanpeckel's Achievements


Apprentice (3/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. Hmmmm... just revisiting this AGAIN. The issue has popped up on another machine here. I'm wondering if the issue may be related to this - http://help.filemaker.com/app/answers/detail/a_id/7644 EXPLANATION: The registry for toolbars increments 2 entries per launch. When the application has been launched and quit ~1000 times, FileMaker Pro will no longer launch. I have run the batch file on the users machine and will post if that seems to fix it. If anyone has any other suggestions I'm very open to them. This is like the issue that just won't die! Regards HP
  2. Yeah, I'm beginning to think the only way I'll solve this chestnut is to replace all of our PC that were made in the 70's. We've never had the issue on newer hardware. Ugghhh...
  3. So, I now have the need to revisit this topic (unfortunately). After much mucking about, we ended up resolving this issue by buying three new PC's. The way I figured it was the machines in question were about 5 years old, and well and truly due for upgrade anyhow. Now we have three new machines all running sweet. BUT there are still a few old ones about and these old machines are now having this problem. I have tried the above suggestions - FM client update, OS update, FM reinstall, checking versions of plugins, basically everything above. Also there's a registry fix I tried - http://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&frm=1&source=web&cd=2&ved=0CCYQFjAB&url=http%3A%2F%2Fhelp.filemaker.com%2Fapp%2Fanswers%2Flist%2Fsearch%2F1%2Fkw%2Funsupported%2520operation&ei=QPpGUI3fDc6fiAes7YGYAg&usg=AFQjCNFjPpYN7QL5bHUZ_oiIwxXKIYIXNw No real change. Wim, you bring up a very good point - all the machines that have been having issues, although C drive and RAM have been ok (100G spare, 2GB RAM), they were certainly old bangers. This is the case with this current issue. Does anyone have any other suggestions? Regards HP
  4. So far Vaughan, increasing the cache size has worked, but it's early days I guess. I upped it from 8mb to 16mb. Thanks for the advice and I'll post an update if it remains stable, otherwise I'll look into the other options. Cheers! HP
  5. Ahhh!!! Thanks for the response Vaughan!!! You bring up some very interesting points. I will check all of the options you have mentioned, the cache size being the first as it will be pretty easy! So, if the database has corruption, would you not expect other users with similar roles would experience the crashing as well? As far as I know everyone else is running sweet. I will check with our FM dev guy and ask him about possible FMP 11 features. This is a distinct possibility as we are currently preparing to upgrade to 11 or 12. Thanks again. I now have a glimmer of hope to cling to again :laugh2:
  6. Folks, I'm having an absolute shocker here with users reporting Filemaker crashes throughout the day. We are running Filemaker Server 10 on a Win2K3 SP2 platform and we have a mix of clients on OSX and XP. Three of the windows clients are having issues where they do seemingly unrelated things and Filemaker will crash. The error messages received are - "An error occured during this operation" (very descriptive) and "An unsupported operation was attempted" (again...) Also we get the generic "Filemaker Pro.exe has encounted a problem and needs to close", windows thing. It is happening on three PC's, the other 40 or so are ok. I have tried the following things to fix them - Removed and reinstalled Filemaker (including deleting the original program file folder) Updated the installed filemaker with 10.0v3 (the rest of the machines are on 10.0v1) I have also patched the machines to a (fairly) similar level of a known working machine. I even pulled the HD out of one of the buggy machines and put it into a similar machine (cause the original machine died), but this still bugs out. I'm kind of at a loss now as to what else I can try. If you have any thoughts or suggestions I'd love to know! Thanks in advance! HP
  7. Yep, fair enough. I've just googled a bit more and nobody seems to have developed such an XSLT stylesheet. "The XML in JDF is quite complex and you would need a XSLT to convert Filemakers default output XML into something structured to JDF conventions. This XSLT would be worth it's weight in gold and to write it would take a long time. A few years ago, I searched for such an XSLT but never found anything. In the end I gave up, trashed our FMP order tracking system and our company bought a ready made system (which, by the way, doesn't work as well as the Filemaker and doesn't work with JDF)" Oh well...
  8. Well, yeah, technically "it" (whatever it means) is based on XML, but not entirely. XML with a schema basically. Some MIS systems have the ability to generate JDF/JMF. I was wondering, no, I was HOPING, Filemaker was now one of those.
  9. Folks, Does anyone have any info on JDF/JMF in Filemaker? I know this couldn't be done too easily about four years ago, but now? Anyone...? Regards HP
  10. Yeah, you're absolutely right Vaughan! It's a jungle out there (out past the firewall). Anything can happen.
  11. Thanks for the reply guys! Vaughan - yeah, something seems to be happening to it along the way. The odd thing is that if she were to send it again, it would go through ok. Brian - yes, the email is sent via the users mailbox. The thing is, in her sent items, the PDF appears fine. It really has me stumped. Maybe this is more a general email question than a Filemaker specific one.
  12. Folks, We are having random issues with a Filemaker email script that attaches a PDF of a quote to an email. 95% of the time they go through as they should, no problems. Occassionally however, different clients are getting this as their email - ------=_NextPart_000_017B_01CD0113.9FXXXA0 Content-Type: application/pdf; name="REMOVED.pdf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="REMOVED.pdf" JVBERi0xLjQNJeLjz9MNCjEgMCBvYmoNPDwvUGFnZU1vZGUvVXNlVGh1bWJzL01ldGFkYXRhIDQg MCBSL1BhZ2VzIDIgMCBSL1BhZ2VMYXlvdXQvU2luZ2xlUGFnZS9PcGVuQWN0aW9uWzYgMCBSL1hZ WiBudWxsIG51bGwgMS4wXS9UeXBlL0NhdGFsb2c+Pg1lbmRvYmoNNCAwIG9iag08PC9TdWJ0eXBl L1hNTC9MZW5ndGggMzI4NC9UeXBlL01ldGFkYXRhPj5zdHJlYW0NCjw/eHBhY2tldCBiZWdpbj0i etc etc etc NOTE: I changed the filename to REMOVED for security reasons There doesn't appear to be any pattern to it as far as I can see. We could run the Filemaker script again and the client would receive it ok. Also, in the person who ran the script's sent items, the PDF appears ok. Any thoughts? Anything? I'm at a complete dead end here. Any help much appreciated!! HP
  13. OK, so this could be the most stupid question on this forum, but why can you not script Filemaker using an EXECUTE SQL statement to insert data into your mySQL DB ? Never tried it but that was the way I was hoping it would work. Feel free to set me straight.
  • Create New...

Important Information

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