Jump to content


  • Posts

  • Joined

  • Last visited

Alpha-Snail's Achievements


Enthusiast (6/14)

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

Recent Badges



  1. I have a runtime that I deploy to various users. Each time a new user opens my solution for the first time they are forced to manually locate and enable the text formatting toolbar, then move it to the proper location. They are also forced to manually select "Enlarge Windows Content to Improve Readability". I can not find a way to auto enable these settings in advance. Even if I build the runtime with these enabled, my solution installs with them disabled. I even tried opening the runtime build and making sure the settings are enabled before deploying. Still, when ever it's installed on a different machine my solution opens with these disabled. Is there any workaround to these two seemingly related issues?
  2. How do you print multiple pages in web viewer? If you drag the field below the first page in fm, the remaining pages printed are blank. Anyone got a work around to this?
  3. I've developed a professional application that has many great features. One addition that I would like to add is the ability to import sales leads from various lead source companies. Since each file format is in a sense "proprietary" to each company, am I legally obligated to gain their approval before scripting a solution that I provide to others?
  4. Here's another way you can go. I think it's the PERFECT solution, but you be the judge. It's called 'Copyminder'. I use it in my runtime solution and it works extremely well. The way it works is that it encrypts the .exe file. Then, whenever the user runs the application, Copyminder checks to see if this is a valid installation. If it is, no problem, if it isn't it flags the installation and watches it more closely. Depending on the setting you use, you can have that installation disabled, either temporarily or permanently. Users should have access to the internet, but it isn't absolutely necessary. Also, while accessing the internet seems like a EULA violation for a FM runtime, it actually isn't since Copyminder does the accessing, and since it dosn't actually pass any data on to the runtime. The result is that you are perfectly protected in all situations. If someone gives away their copy you will know about it, and the "giver" runs the risk of having their copy disabled by Copyminder. Instead, they should download a new copy of the FM Runtime. When they do, they are required to register, which means you know who they are. And if they give faulty data, you can immediately disable that copy of your runtime. Also, if the user needs to move their runtime solution to another computer (ie. hard drive crash), that isn't a problem either. Finally, there is no additional coding required on your part. Their solution is extremely well thoughtout and effective. Visit www.Copyminder.com. The company that runs it (Microcosm) has been doing software security since the 1980's. They're also very good to work with. This may be THE most dynamic, flexible yet strongest security solution out there.
  5. Does anyone have any experience with the Copyminder security system? Seems pretty state-of-the-art for securing Filemaker applications. They provide a plugin that's FM7-8 compatable. FYI: Their site is: www.copyminder.com. Thinking about using it, but would like to know what others think. Thanks.
  6. I am trying to create a template that allows users to click on a number of buttons to create a customizable template for emailing. The "Email Campaign Management" application that comes with FM8 does exactly what I want in this respect (and a whole lot that I don't want in others), but I'll be honest in saying that, despite my knowledge and experience in FM, I don't know how they did it! : If after creating the layout with buttons and a field that gets populated with them, how do you convert that into a field that merges the data? For example, if I have in the template "Dear ...", how do I convert that to "Dear John" for one record and"Dear Jane" for another? Any help would be greatly greatly appreciated!!! Ron
  7. A very simple question, really. I thought standalone runtimes could, and I though I had tested that out some months ago. But now I can't seem to get my FM8 standalone to execute the import script. (The data is simple comma delimited text.) Does anyone know the answer? Thanks for your help.
  8. I am having trouble getting FM8 to Import from Excel 2002. It works as an FM Pro application, but when I convert it to a runtime it doesn't execute the script. Is this a limitation of FM or am I making some kind of mistake that I'm not catching? Thanks!
  9. Update - I resolved the problem, although it is only a workaround. Since FM can still see worksheets, I had to create a separate one, just for my data. Beginning with cell A1, I created lookup formulas that referenced the actual data on another worksheet. Then I refered to that sheet in FM. Problem solved, although I believe I have found a bug in either FM or Excel. (Problem seemed to have occurred after protecting the worksheet. Unprotecting it had no effect on the problem.)
  10. I am unable to get FM to see all the ranges that I defined in Excel! (There are only about 7 of them.) The ranges are defined correctly, my filepath to the Excel file is correct, and the Excel file extension is selected in Filemaker. All Filemaker sees is the worksheets, not the ranges.
  11. Update: I have an idea, though I haven't tested it yet... The solution may be to skip the merge-perge effort and to run an import script multiple times, once for each table, beginning with the main one. The key is to let the original import do the merge perge via FM's import settings, then reimport the other tables as updates. Comprende? Not very eligant, but it may work. (Then again, it may not!) B)
  12. I have a fairly large number of fields (126) that I am importing. These fields belong in a variety of different tables within my application, therefore the only way to bring them all in at once is via a separate dedicated table. I then need to be able to move that data to the different fields where they really belong. The only problem is that some imported records may be partial duplicates of existing ones in my database (requiring an update of that data), while others may be new records. How can I begin to manually script this merge-purge procedure?
  13. Check out the iMailer plugin. It'll do the trick very nicely.
  14. What a great use for the "On MouseOver" events! Here's two ideas that could perhaps be useful to many: 1.)To provide additional information in a portal. The developer could create a script that would pop up a tool-tip with additional information, unique to each record that appears in the portal. Could look pretty impressive. 2.) Here's an even better idea! There's a fantastic website for creating free and easy to use Glassy Buttons. Works even for Windows based FM aps. It's http://www.netdenizen.com/buttonmill/glassy.php. I use it on one of my Windows based FM applications and they looks great! The only problem is that you can't "roll-over" the graphic image in the Windows version of Filemaker. Maybe with your idea you can. (I'm not sure how you would script it though.) ;)
  15. Gaston, Let me again thank you for both creating this great plugin and for your help in understanding it last weekend. I have found what appears to be one small caveot (I don't consider it a bug), however. I discovered it when renaming a file that uses the plugin. I changed the name from "FileName 1" to "Filename 1.1". The result was that the script that worked before stopped working completely. There are, of course, 3 ways to tell EvenScript the file name: "Get(Filename)"; the name of the actual filename (in quotes); or the name of the filename in a field (and not in quotes). I tried method one and three. Don't know about the second one. Anyway, it's not a big deal. Just don't enter that second dot in the filename.
  • Create New...

Important Information

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