Jump to content

elipsett

Members
  • Content Count

    63
  • Joined

  • Last visited

Community Reputation

0 Neutral

About elipsett

  • Rank
    member

Profile Information

  • Gender
    Male
  • Location
    Kumamoto, Japan

Contact Methods

  • Website URL
    http://www.kurodahan.com

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    13 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    10.9--10.12, Win7

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Having a bit of trouble getting the find function in a script to run. I can't really post the script here because I'm using the Japanese-language version, and most of you wouldn't be able to read the text, but the only problem is with the find function. I have two tables in a single DB. Table A is list of people I need to pay, each person with a unique ID (text). Each record is marked with that ID, and a calculated field saying "Paid" or "Unpaid." This list is used to actually calculate the total amount payable to each person that month. Table B is a list of payables, each record for a single payable, and marked by amount and ID. The script is supposed to go through the list of payables, one at a time, and only see if that ID already has an open (Unpaid) record in Table A. If there is a record, the script loops and moves to the next record in Table B, repeat. If there is no record in Table A with that ID marked Unpaid, then the script creates a new record in Table A with that ID and marks it Unpaid. The script looks at the current ID in in Table B, and assigns it to a variable $$ID. Goto Table A and search for ID=$$ID AND Status=Unpaid. This is where the problem occurs. If there is a matching record, it is found correctly, and the program correctly ignores it, whether error capture is on or not. If error capture is OFF and there is no matching record, FMP returns an error message saying no records match the criteria (correct). If error capture is ON and there is no matching record, FMP says error code=0 and Record count = 1 (the screen at that point shows a layout with no ID displaying). Prior to the FIND, the DataViewer shows the correct settings for ID and $$ID. If I search for either criterion the script works, but I need to search for both. I've been trying to capture either the error code (401) or find count (should be zero), but they always return Error=0 and Count=1 whether the matching record exists or not. Obviously I'm overlooking something. I think that's enough information... Any suggestions on what I did wrong? Thanks for your time.
  2. Thanks. I read the documentation, too, but since they open each other's files fine, I had to ask.
  3. I've been running FMP13 and FMPAdv13 on Win7 and MacOS10.x platforms, and finally have to upgrade my hardware. I bought a few copies of FMPAdv17 to see how it works, and as far as I can see it will open and run the old FMP13 files, using the same filenames and extensions (fmp12). After a file is created or modified by FMP17, it can still be opened and run normally by FMP13. It would be great if I could access the files using both FMP13 and FMP17 clients. I don't use Server, just have a machine on my network running a standard FMP13 client. Unfortunately, it looks like FMP13 cannot open any file hosted by FMP17, and visa-versa. But since the actual file structure seems to be the same (ignoring new functions unsupported in FMP13), I can't see any reason why they can't host each other's files. Is it flatly impossible? Or is there something that can be done to one or the other? Thanks for your time.
  4. I've been using FMP13 on MacOSX 10.12.6 with Apple Mail to send FMP-generated emails with attached PDFs. I recently switched from Apple Mail to Airmail, and it is now impossible to send emails from FMP. Does anyone know if Airmail can send mail with attachments on Sierra MacOS 10.12.6, if I upgrade to FMP16? That's the only reason I might really need to upgrade, and since upgrading to FMP16 will also require a few new computers to run the new OS that the new FMP demands, I'd rather not spend all that money now if I can avoid it. Thanks.
  5. Apparently the problem is a missing permissions manifest in main jar, according to error information: java.lang.SecurityException: Missing required Permissions manifest attribute in main jar: http://localhost:16000/admin-client-lib/admin-console-client.jar at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source) at com.sun.deploy.security.DeployManifestChecker.verifyMainJar(Unknown Source) at com.sun.javaws.Launcher.doLaunchApp(Unknown Source) at com.sun.javaws.Launcher.run(Unknown Source) at java.lang.Thread.run(Thread.java:744)
  6. I made the silly mistake up letting Java update itself, and now of course FMS won't launch. I've cleared the Java cache several times, rebooted several times, and no matter what I do the app still says it won't launch. Is there any fix known for this? It would be really nice if I didn't have to reformat the whole system again just to get it running. Any suggestions welcome. Thanks.
  7. Thank you. That does indeed seem to be what I'm looking for. I'll go ahead and plug it in later today and see what happens.
  8. Numbers reported in sub-summaries in reports are automatically rounded. It would save me an enormous amount of time and effort if there were merely some way to convert those numbers to integers. Since they are showing up in reports, though, it seems to be impossible to perform any calculations on them, and for other reasons it is difficult to convert to an integer elsewhere. Alternately, if it is possible to capture a number displayed in a sub-summary into another field for manipulation that might work too, but again because this is in a report every time I try to capture the number, I end up capturing a number representing the entire found record set, not just the subset I need. The non-integer number displays perfectly for each sub-set in the report, but I can't find any way to convert that displayed number into the integer value I need. I welcome any suggestions, but it would be enormously difficult to create a sample DB to short you exactly what is involved. Thanks for your time.
  9. elipsett

    'sliding' portal?

    I don't understand fully how it works, but it does indeed work. Thank you very much for your time!
  10. elipsett

    'sliding' portal?

    Thank you, Dan. I got sidetracked by a customer who couldn't seem to locate his posterior with both hands, but should be able to get back to this shortly. I understand what you're saying, and will try it soon. Probably tomorrow.
  11. elipsett

    'sliding' portal?

    All jobs have at least one job item. A sample list might look like: Joe Bloe - January 2012 --Job No. 1 ---Cleaning skyhook ---Installing new skyhook --Job No. 2 ---Loafing about - March 2012 --Job No. 1 ---Rinse and repeat I can display all this just fine using reports and sub-summaries now. The trouble is getting that lowest level (---) to display all items, but no blanks. It does not have to be handled with portals but that seems to be the only approach that offers me a chance of getting what I want. I don't completely understand your suggestion. This is a year-end report for contractors. We generate one report for each contractor, breaking down jobs and job descriptions within. Can you explain a bit more clearly? I am only beginning to get into reports and a lot of it hasn't gelled yet.
  12. elipsett

    'sliding' portal?

    This seems to be what I need to know. I am printing year-end pay reports for people we pay money to, and the information in the body is displayed using a portal. Each person receives one report for the prior year, listing payments for each month, and within each month by each individual job, and within each job by individual job items. The last item (job items within a given job) is displayed using a portal. Everything else works fine, but the only way to display multiple job items for a given job is to set the portal to display a large number of records. Most people only have one job item per job, which means all those blank lines take up a lot of space. Is there any way to dynamically set the number of portal lines displayed based on the number of records it will display? So if there is only one job item, the portal will be only one line high. If there are 10 job items on that particular job, the portal window expands to hold ten lines. Thanks.
  13. Gee, that was pretty obvious, wasn't it? I was looking for the pretty top menu displayed in the WIndows version and never noticed. Thanks for the help!
  14. I recently had to switch to a new Mac, how running 10.7.5, and moved my copy of FMA11 over to the new machine, then updated it to the latest 11.0v4 version. The new installation works normally in every regard EXCEPT there is no menu bar in the Manage Script window, and when editing a script there is no script copy/paste option shown. In other words, it seems to have installed as standard FMP11, not FMA11. The CD is correct, the serial is correct, and it is only installed on two machines, and the other installation is on a different network (my home). The same CD was used to install into my home Windows XP machine and the prior Mac 10.5 machine, and worked perfectly on both. Still works perfectly on the XP system at home. I have deleted and re-installed twice into the Mac system with no change. Any suggestions? (Including "try posting in the xxx forum" if this turns out not to be the right place...) Thanks.
  15. OK, I have a better idea of what the issue is. When I set the script to send the email via SMTP direct, it works perfectly, with CR/LF where they are supposed to be. When I set the script to go through my email client (Outlook), all the CR/LF codes are stripped out. I haven't been able to find any setting anywhere in Outlook or FMP that might have any effect, unfortunately.... I say unfortunately, because unless I can see each email one at a time and make sure it says what it is supposed to say, it'll be a royal PITA to debug the whole script...
×
×
  • Create New...

Important Information

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