Chris Williams

Mine kept crashing (or unexpectedly quit) when I opened any database. turns out that one of my plug-ins isn't compatible. I haven't checked which one yet. If you cant open you DB, try disabling your plugins and try it again.

I think the problem I was running into was making everything a calculation. I ran into a circular definition every time. I finally wrote a script to step through each payment line item and used temp fields to look at the previous lineitem to determine the correct amount. So far it seems to be working.

Yay for locals! I'm talking about charging late fees for customers with NET terms. I have customers who are notoriously late in their payments. How would I book the charges? I can figure out in a calc field, but it looks like my approach is too simple for what I'm trying to get.

I hope I have the right topic forum. I've run into a problem thats causing a migraine and an ever-asking boss (may be related). Charging an invoice isn't the hard part. That's simple math as far as I can tell. But it seems taking a payment on a late invoice with an interest charge gets complicated. If I take a payment that includes the interest charge the balance goes negative. I can't tell if I am looking up the interest incorrectly or if I'm looking at the wrong balance. Is there a standard practice for both cases? I'm not having much luck with the google search. Thanks

You dont suppose there is another way to set the values for Page Setup? Say Applescript or something?

Well! I figure this out well enough. From talking with the folks that use the databases, some of the databases were fine, just a few were slow. Turns out "rebuilding" two of the big ones that the other were looking at fixed it. A good lesson in FMS rules. I had to open the databases after rebuilding them. It also explained why they weren't backing up to the back up drive successfully. I dont know, however, what caused it.

I am at a loss. Seems just recently our databases are running at a snails pace. Wasn't my idea, but our system is FMS 5.5 v4 on 10.3.3 XServe and the files are on a XRaid. Everything has been running really well for about two weeks, in fact faster than our previous set up. But now using the databases takes a really long time and everyone who uses them can't get their work done, etc etc. Any common problems that I'm overlooking?

Is there a known/proven way to find a corrupt layout? Using Mac OS X and FM Dev 6.

tell application "Print Center" set printerlist to (name of printers as list) end tell tell application "FileMaker Pro" set the cell "Printer List" of record 1 of database 1 to (printerlist as list) end tell

I'm going to go ahead and answer my own question. The trick is using a repeating field. In this case, I have a FM Field "Printer List" with a round number of 10 repetitions. And this was the code I used in this case. tell application "Print Center" set printerlist to (name of printers as list) end tell tell application "FileMaker Pro" set the cell "Printer List" of record 1 of database 1 to (printerlist as list) end tell

I'm relieved that Print Center is so AppleSciptable! One thing, I cant get is the list of printers in the list. Strike that, I can get the list, but when I put it into Filemaker is comes out all in one line. How do I get the list with a rtn after each printer?

I have run into interesting bugs with FMD 6. Have you done the process of elemination? Like telling Print Center to set a variable?

While my knowledge of AppleScript is limited, how it works with Filemaker is even more so. I'm trying to get certain values into a field and I've come across a few different ways to do it. 1 - set the cell "fieldA" of record 1 of database 1 to (varA as text) 2 - set the field "fieldA" to varA as text 3 - set the cell "fieldA" of current record to (varA as text) They seem to do the same thing. But I've noticed that when I'm using it in a FM Script from calc field, example 1 cause the FM Script to basically skip over the AppleScript, 2 only works on my machine and not my client's, and 3 I have yet to test on my client's but work fine on mine. Is there some official logic to all this?