titanium76

I just saw it for almost nothing on ebay. Item # 150499847126 just in case anyone's looking.

This used to work under 10.5.x, it would list all the local and networked printers when executed as a calculated applescript: "tell application " & Quote("FileMaker Pro") & ¶ & "set theDoc to item 1 of (documents whose name starts with " & Quote(Get ( FileName )) & ")" & ¶ & "set cell "& Quote("LocalPrinterList") & " of current record of layout " & Quote("devOfficeLocations") & " of theDoc to do shell script " & Quote("lpstat -a") & ¶ & "end tell" Now I get "A "" can't go after this identifier." Unknown error -2740. HOWEVER, if I take that script, paste it into FileMaker's Data Viewer it shows me the calculated AppleScript: tell application "FileMaker Pro" set theDoc to item 1 of (documents whose name starts with "ION") set cell "LocalPrinterList" of current record of layout "devOfficeLocations" of theDoc to do shell script "lpstat -a" end tell which if run in AppleScript Editor, works fine and pastes the result into my filemaker file. Any ideas?

:idunno: In the past I used a simple applescript to call on the Printer Setup Utility to switch printers. Leopard ditched that app and has totally integrated it into System Preferences. Does anyone know a way to access those settings via applescript? Better yet, how about a terminal command? :idunno:

Same thing here. I believe it's a Leopard issue.

I know that Date ("string") will always return an error... let's pretend that a user entered "Last Monday" instead of 1/2/2000.... is there and error capture where i can allow errors to result as the text they were entered as?

I understand it will fail. That is my point. Can I catch the error w/ something?

Ok, if I do this calc in a calc field and result text: Date("NonDateText") I get a result of "?" so, is there a way to capture this error and with a case statement offer an alternative answer?

Sorry for all the confusion.... We enter fields for real estate documents. Occasionally they are recorded without a day added to it. For example, a Deed would be dated January _ 2007. We need to report that the day is missing by using "_" instead of a number. My current solution is: Case( Left(EntryField;1) = "*";EntryField; ReferenceField = "Date and Time"; Let ( [ posval = Position ( EntryField ; "@" ; 1 ; 1 ); lenval = Length ( EntryField ) ] ; Case(IsEmpty(EntryField); EntryField; TrimReturnsSpaces (TextFormat ( Date2Text(Left(EntryField; posval-1)) & " @ " & Right ( EntryField ; lenval-(posval+1) )); True )) ); ReferenceField = "Date"; Date2Text ( EntryField ); ReferenceField = "Dollar Value"; DollarFormat (EntryField ); ReferenceField = "Text"; TextFormat (EntryField ); ReferenceField = "Consideration"; DollarFormat ( Filter ( EntryField ; "1234567890$.," )) & If(Right ( EntryField ; 1 ) = "c"; " & c") ; TextFormat( EntryField)) I am looking for a way to avoid placing an "*" at the beginning of the string and instead have the calculation know it errors. The results work like this now: 1/2/2006 calculates to January 2, 2006 1/_/2006 calculates to ? ?, ? *1/_/2006 calculates to *1/_/2006 *January _, 2006 calculates to *January _, 2006 Is there a way to do something like: Case(IfError(Date2Text ( EntryField ); EntryField)

I have a field that calculates the date into text: 1/2/2006 changes to January 2, 2006 easy enough, but there are instances where the day may not be available, generally because it was omitted from the document, so I need to be able to manually enter it as January _, 2006... I added a catch to the calc that if the left most character is an "*" then the calculation isn't activated and the "*" is automatically removed when printed.... ex: *January _, 2006 But I would rather do it differently. If I enter 1/_/2006 I get ? ?, ? is there any function that can look at the calc and see if it will fail instead of me using the "*" to force it not to calculate?

I don't get it. Script triggers have been on the wish list forever... I have waited for 9 before building a solution that will NEED triggers. I understand there are solutions out there, but the oversight on this since version 7 seems almost purposeful.

I'm fat and needed this to work -but - there was a failure to decompress. My life's story. :badidea:

We have used a FileMaker - Applescript - PageSender solution for the last 2 years. Either all the fax-modems in Mac's are sub-par or PageSender still needs help. Yes, the scripting is nice, but the stability is not there - yet.

But why? I find all these solutions, honestly - stupid. FileMaker 8.01 should have a fix for both Tab scripting and calculated naming. This is such a hot topic, I can not believe the geniuses at FileMaker missed this one. How can it possibly be such a robust cross-platform product with such a MAJOR oversight? Bizarre... Anyway, I must agree with the others who recommend NOT using a hair-brained trick to make it work. Eventually you will encounter a problem or simply have a poor design.

This trick is potential suicide for any real database design.

How can the Tabs feature not be scriptable? How can I not use a calculation to name my tabs? Will there ever be a stock Get(TotalPageCount) function? Don't get me wrong, Filemaker 8 Advanced is great - but some of the simpler things seem to have been overlooked. A questionable Tab trick of using a Go To Field works, but at what cost? Oh well...