Jump to content


Highest Reputation Content

#386923 enter into valuelist

Posted by LaRetta on 16 April 2012 - 07:25 PM

Ya know, when you rate people with negatives, they will stop assisting you. Wouldn't you in their place? Why should we risk responding just to get slapped for it if you simply don't care for our response? You are judging whether our answers are right or wrong and you know very little about FileMaker. Would you let a podiatrist take out your gall bladder? No - you listen to those that know what you want to know.

Soon, at this rate, you will have nobody left to help you. By the way, I am not responding ... I'm afraid to. :cry:

Also, don't tell people to read the post again ... that is insulting. People here READ the posts. Your posts have been almost impossible to understand at all. That is not our fault. It is yours.
  • 6

#387207 interface check

Posted by BruceR on 19 April 2012 - 07:38 AM

Don't touch FileMaker again. Hire somebody who know what they are doing.
  • 5

#384411 Creating a separation model from an existing solution

Posted by LaRetta on 12 March 2012 - 07:49 AM

No, you can't have pure separation. And yes, you might have to make more changes in the data file if your solution is still young (and occassionally throughout) but that is easily off-set by time saved not migrating. I've designed some large systems using both separation and not. Here are the reasons that *I* prefer using separation and these reasons probably aren't the top reasons at all - but they are important to ME:

Transfer of Data (the best solution is NOT moving data)
If you use single file and design in another version (so Users can continue working in the served version) you have to migrate the data from the served file to your file and that can take hours even when scripted. Every time you move the data, you risk something going wrong and the likelihood increases each time you migrate.

With separation, the data file remains untouched.

Import Mapping (unsafe and time consuming)
Scripting the automatic export and import on every table in the single file solution takes time as well. Every export and import script must be opened and checked because you have added (and probably deleted) fields. You can make a mistake here. And even if you don’t, the 'spontaneous import map' bug might get you. It is very time-consuming and difficult, dragging a field around in the import maps (FM making it very difficult with the poor import mapping design).

No data export/import or mapping with separation.

Data Integrity (and User Confidence at risk)
When working in a single served solution, you risk records not being created when scripts run (if you are in field options calculation dialog), triggers firing based upon incorrect tab order that you just changed on a layout, and a slew of insidious underground breaks most that you will never see until much later. By then, all you will know is that it broke but not why. You risk jangled nerves and lost faith of your Users who might experience these breaks, data loses, screen flashes and other oddities. A User’s faith in your solution is pure gold and it should not be risked needlessly.

External Source Sharing (provide ‘fairly’ clean tables for integration needs)
It has been discussed many times … why we have to wade through a hundred table occurrence names (particularly if using separation model anchor-buoy of which I'm not a fan anyway) and also have to view hundreds of calculations (which external sources don’t want). It can be a nightmare.

Much better with a data file – where calculations are kept to minimum and the table occurrences are easily identifiable base relationships and easy to exchange with MySQL, Oracle and others. If FM made calculations another layer (separate from data) then FileMaker would go to the top instantly … rapid development front-end and true data back end. But I digress …

Crashing (potential increases when Developing in live system)
Working in developer mode (scripts with loops, recursive custom functions), means that there is higher likelihood of crashing the solution when designing - admit it. If you crash the solution while in the schema, it is (usually) instant toast but regardless, you SHOULD ALWAYS replace it immediately (run Recover, export the data and import it into a new clean clone).

With separation model, you never design live so it is moot. No trashed file means no recover and no migration. You are designing as we all should … on a Development box.

Transferring Changes (even if careful)
Working in live single file system, a change you think is small might have unseen and unexpected side-effects. That potential danger increases as the complexity of your solution grows. This is why we all should beta test changes before going live. But even if careful and even if you design on Developer copy and test it, document your changes and then re-create those changes into the served file (eliminating the data migration portion completely), you risk mistyping a field name, script variable, not setting a checkbox and so forth.

Separation also can risk error because it can mean adding a field or calculation to the Data file but it is very small percentage of the changes we make (except very early); most changes are layout objects, triggers, conditional formatting…UI changes. It is more difficult to replicate layout work between files. And most changes in the data file occur before the solution is even made live the first time.

Same Developer experience (Developer works in single file regardless)
In separation, all layouts and scripts reside in the UI no matter how many Data files are linked as data sources. The only time you have to even open the Data file is to work in Manage Database. Added ... or set permissions.

Fewer Calculations (means faster solution?)
If one decides to go with Separation, the goal is no calculations or table occurrences in the data file but that goal is not obtainable. Since this is your goal, you try to find alternate methods to achieve the same thing to avoid adding calculations (which you should do anyway). You will use more conditional formatting, Let() to declare merge variables, rearranging script logic to handle some of it … there are many creative options. And once you start down that path, you will find that you need fewer calculations than you ever imagined.

Separation model means I can work safely on the UI aside and quickly replace it while leaving the data intact with the least risk. Some calcs need a nudge to update and privileges must be established in the data file as well – those are the only drawbacks I have experienced with it. I have never placed the UI on local stations. I have heard (from trusted sources) that it increases speed. There was a good discussion on separation model here: https://fmdev.filema...age/65167#65167

Everyone has their opinion. I did not want to go with separation and I was forced into it the first time (by a top Developer working with me, LOL). I am glad I was. Once I understood its simplicity and that everything happens in the UI, I was hooked. Of course if it is a very small solution for one person then I won't separate but for a growing business with data being served, I will certainly use it.

Next time that, in your single-file solution, you go through a series of crashes because of network (hardware) problems and you have to migrate every night, think about separation. Next time you need to work in field definitions but can't because Users are in the system, think about separation. Most businesses are constantly changing and that means almost constantly making improvements to a solution. You can NOT guarantee that changes in Manage Database or scripts will not affect Users in the system.

Risk is simply not in my dictionary when it comes to data. Enough can go wrong even when we take all precautions. I don't dance with the devil nor do I run with scissors. :laugh:

Joseph, I think it would be easier to start from scratch because it makes you re-think each piece. And, as you learn, you will find better ways of re-creating each portion of it. I would also wait until the next version arrives to take full advantage of its new features. It won't be long now.
  • 5

#431747 "Boolean" checkbox trouble

Posted by LaRetta on 08 December 2014 - 05:50 PM

I suggest that every act which could have been optimised but wasn't is poor practice.  It is not poor practice because of principle but rather because of:

  1. If you let slide optimisation in this area on 2,500 records, the next time you'll be inclined to think letting slide with 3,000 records is fine.  It is a slippery slope which breeds sloppiness and drags a good solution down into less than ideal.
  2. We can not always predict the environment and venue our solutions will be fired under.  It may be fine over LAN but when accessed from an iPad with low-grade provider, the process which only took a blink over LAN now takes 4 seconds and THAT is a LONG time to a User.  As for me, if I go to a website which takes more than 6 seconds to load, I move on.  Users today will not tolerate slop.  Compounded, each of the blow offs which were small, now each contribute to network traffic and begin to crawl.

Do not give in.  Optimize everything you do at all times.  It is one of the few things you can control and it is the best investment in your solution.  You may think you are only saving one second but multiply that over six months, performed by 25 users and you see clearly where this is going.  Do not fall for the disease of sloppiness.  Commit to excellence in your work.


And yes, it is only my opinion because my opinion is the only one I have to share.  And yes, I'm an obnoxious idealist.  If that is the worst I am called, I'll take it.

  • 4

#426995 Grey background in layout mode

Posted by Raybaudi on 23 August 2014 - 11:05 AM

do you have an idea, how can i change to the normal view?

Your "Maior Grid Spacing" is setted to 1 point.
You need to change it to something like 10 or more.
Or you need to unchek the box: View >> Grid >> Show Grid
  • 4

#426834 how to start with server if stupid

Posted by Ocean West on 19 August 2014 - 05:49 PM



Since the best experience is if the end user has all the data they need local to their iPad and not rely on connectivity you may try to do this:


Create your solution in ONE file with multiple tables one table for your catalog another other table for your customer data entry. 


If your catalog only changes every so often that is fine you can push out a new version to the end user to replace their database with all the catalog data.


If they only need to add new customers and not look up historical customers then you can essentially have them email data (export as TAB/CSV/or EXCEL )  from the customer table for you to import in to your own file, every night.

(not ideal but its a work around)


Since cost is a concern for you please look at this http://fmeasysync.com, its a free open source framework for syncing your database - it may be a bit overwhelming at first but I am confident that you can get there!




Charity every year at the developer conference we (old salts) wonder where the "next generation" of FileMaker Developers are coming from, if you have a passion for this and

accept the challenges head on, you most likely will be reciprocating your learnt knowledge and wisdom in short time to other newbies jumping in to the fray.




What goes into the External Data Sources - really depends on where the files will ultimately be deployed, if two files are hosted then they would use relative paths:


if one file is local to a device then it needs the fully qualified URL path with either the PUBLIC IP address, or a domain name, if using a 10.0.x.x or 192.168.x.x this is an internal IP address and wouldn't be accessible out side your environment.


if you would like to see how can be access when hosted please send me a private message and I could host a sample file for you that you can test with. 



  • 4

#423790 Display theme in Manage Layouts

Posted by LaRetta on 19 June 2014 - 07:05 PM

I know this is lower priority than some of the other wishes but I can't help but just mention it ...


If we go to Manage > Themes, we see a list of themes loaded in this file and it also indicates how many layouts are assigned to that theme.  But it would be nice if we knew which layouts were assigned to a theme and even had the ability to ... yeah I know ... probably never ... but to GTRR (so-to-speak) to those layouts or see a list of them at least.  Manage > Layouts certainly has room to list its theme along with the table and menu set.  If nothing else, this would make life easier for us.


When a solution has 150 layouts, it can take quite a bit of time to go through them all to find the few layouts assigned to a theme needlessly.  And each theme (even themes unused), load all definitions and take up quite a bit of space.


For instance, a recent example - file had 13 themes but on 3 were used.  By converting them all to the single theme, I saved 1.7MB right off the top and it took 15 minutes.  So a way to quickly jump to layouts according to their theme would be helpful.


Or ... am I missing something here?  Are there ways of seeing  a list of layout names per theme?


Thanks everyone for listening and hopefully providing a solution of which I was unaware.  Otherwise I'll provide FileMaker feedback about it.   :laugh2:


Also, there is a Custom Themes forum for FM12 but there isn't one for FM13.  It might be nice to remove the 'FM12' portion from the forum title so we can put FM13 questions there as well ... or ... create another forum for Custom Themes in FM13.  I prefer the former.  


Thank you!!

  • 4

#414575 Script Management Best Practice

Posted by jbante on 02 December 2013 - 06:12 PM

It's perfectly find, even preferable, to keep your process split out into separate scripts. There are plenty of arguments for this from different sources, but I personally think that the best reason is that human working memory is one of the biggest bottlenecks in our ability to write software. It's dangerous to put more functionality in one script (or calculation, including custom functions) than you can keep track of in your head. If you find yourself writing several comments in your scripts that outline what different sections of the script do to help you navigate the script, consider splitting those sections of the script into separate sub-scripts, using the outline comments for the sub-script names. If your parent scripts start to read less like computer code and more like plain English because you're encapsulating functionality into well-named sub-scripts, you're doing something right. (The sub-scripts don't have to be generalized or reusable for this to be a useful practice. Those are good qualities for scripts, but do the encapsulation first.)


I think you'd be better off if the scripts shared information with script parameters and results instead of using global variables, if you can help it. When you set a global variable, you have to understand what all your other scripts will do with it; and when you use the value in a global variable, you have to understand all the other scripts that may have set it. This has the potential to run up against the human working memory bottleneck very fast. With script parameters and results, you only ever have to think about what two scripts do with any given piece of information being shared: the sub-script and its parent script. Global variables can also lead to unintended consequences if the developer is sloppy. If one script doesn't clear a variable after the variable is no longer needed, another script might do the wrong thing based on the value remaining in that global variable. With script parameters, results, and local variables, the domain of possible consequences of a programming mistake are contained to one script. I might call it a meta best practice to use practices that limit the consequences of developer error. Globals are necessary for some things; just avoid globals if there are viable alternative approaches.


There is a portability argument for packing more functionality into fewer code units — fewer big scripts might be easier to copy from one solution into another than more small scripts. Big scripts are also easier to copy correctly, since there are fewer dependencies to worry about than with several interdependent smaller scripts that achieve the same functionality. For scripts, this is often easy to solve with organization, such as by putting any interdependent scripts in the same folder with each other. Custom functions don't have folders, though. For custom functions, another argument for putting more in fewer functions is that one complicated single function can be made tail recursive, and therefore can handle more recursive calls than if any helper sub-functions are called. This ValueSort function might be much easier to work with if it called separate helper functions, but I decided that for this particular function, performance is more important.

  • 4

#411610 How to prevent "scripting error (401)" in server log?

Posted by Wim Decorte on 26 September 2013 - 03:51 AM

Do an ExecuteSQL to do a quick select, if that comes up empty you can skip the real FM find.

It's important to understand though that "Set Error Capture On" does not prevent the error from *happening*.  The only thing it does is hide the error from the user so that you can handle it silently.

If you run the same script in your debugger you will see that FM also reports the error.

  • 4

#408620 is this ironic or not?

Posted by Wim Decorte on 15 July 2013 - 08:12 AM

My 2 cents:


Wherever you state your payment conditions and other important legal info is not the place to try and be funny.

Irony is an interpretation and you can not expect everyone to "get it".  Even if they "get it" you do not want to leave wriggle room from someone to take it literally and pay you in worthless currency.

  • 4

#408606 Server script on computer startup

Posted by Wim Decorte on 14 July 2013 - 12:03 PM

The trick is to use the fmsadmin command line and that syntax is the same on Windows and Mac.  So the only challenge is in calling that fmsadmin command line from your favourite OS scripting language: shell script / AppleScript on OSX and batch file / VBscript / PowerShell on Windows.


Below is a sample VBscript that automates shutting down FMS in a safe way.  It should contain enough pointers to do the reverse.

' Author: Wim Decorte
' Version: 2.0
' Description: Uses the FileMaker Server command line to disconnect
'               all users And close all hosted files
' This is a basic example.  This script is not meant as a finished product,
' its only purpose is as a learning & demo tool.
' This script does not have full Error handling.
' For instance, it will break if there are spaces in the FM file names.
' The script also does not handle infinite loops in disconnecting clients
' or closing files.
' This script is provided as is, without any implied warranty or support.

Const WshFinished = 1
q = Chr(34)  ' the " character, needed to wrap around paths with spaces

' Change these variables to match your setup

theAdminUser = ""
theAdminPW = ""
pathToSAtool = "C:\Program Files\FileMaker\FileMaker Server\Database Server\fmsadmin.exe"


SAT = "cmd /c " & q & pathToSAtool & q & " " ' watch the trailing space

callFMS = SAT
If Len(theAdminUser) > 0 Then
	callFMS = callFMS & " -u " & theAdminUser
End If
If Len(theAdminPW) > 0 Then
	callFMS = callFMS & " -p " & theAdminPW
End If

listClients = callFMS & " list clients"
disconnectClients = callFMS & " disconnect client -y"
listfiles = callFMS & " list files -s"
closeFiles = callFMS & " close file "
stopServer = callFMS & " stop server -y -t 15"

' hook into the Windows shell
Set sh = WScript.CreateObject("wscript.shell")

' get a list of all clients and force kick them off
clientIDs = getCurrentClients()
clientCount = UBound(clientIDs)

' loop through the clients and kick them off
If clientCount > 0 Then
		fullCommand = disconnectClients
		Set oExec = sh.Exec(fullCommand)
		' give FMS some time and then requery the list of clients
		Do Until oExec.Status = WshFinished
			WScript.Sleep 50
		Do Until clientCount = 0
			WScript.Sleep 1000
			Debug.WriteLine "Waiting for clients to disconnect..."
			clientIDs = getCurrentClients()
			clientCount = UBound(clientIDs)
End If

' get list of files and close them
fileIDs = getCurrentFiles()
fileCount = UBound(fileIDs)

' loop through the files and close them
If fileCount > 0 Then
	Do Until fileCount = 0
		fullCommand = closeFiles & fileIDs(0) & " -y"
		Set oExec = sh.Exec(fullCommand)
		' give FMS some time and then requery the list of files
		Do Until oExec.Status = WshFinished
			WScript.Sleep 50
		fileIDs = getCurrentFiles()
		fileCount = UBound(fileIDs)

End If

' all clients and files stopped
' shut down the database sever (does not stop the FMS service!)
fullCommand = stopServer
Set oExec = sh.Exec(fullCommand)
Do Until oExec.Status = WshFinished
	WScript.Sleep 50

' done, exit the script
Set sh = Nothing
' ------------------------------------------------------------------------------

Function getCurrentClients()

	tempCount = 0
	Dim tempArray()
	Set oExec = sh.Exec(listClients)
	' in case there are no clients...
	If oexec.StdOut.AtEndOfStream Then Redim temparray(0)
	' read the output of the command
	Do While Not oExec.StdOut.AtEndOfStream
		strText = oExec.StdOut.ReadLine()
		strText = Replace(strtext, vbTab, "")
		Do Until InStr(strtext, "  ") = 0
			strText = Replace (strtext, "  ", " ")
		If InStr(strText, "Client ID User Name Computer Name Ext Privilege") > 0 OR _
			InStr(strText, "ommiORB") > 0 OR _
			InStr(strText, "IP Address Is invalid Or inaccessible") > 0 Then
			' do nothing
			Redim temparray(0)
			tempClient = Split(strtext, " ")
			tempCount = tempCount + 1
			Redim Preserve tempArray(tempCount)
			tempArray(tempCount-1) = tempClient(0)
		End If
	getCurrentClients = tempArray

End Function

Function getCurrentFiles()

	tempCount = 0
	Dim tempArray()
	Set oExec = sh.Exec(listfiles)
	' in case there are no files...
	If oexec.StdOut.AtEndOfStream Then Redim temparray(0)
	' read the output of the command
	Do While Not oExec.StdOut.AtEndOfStream
		strText = oExec.StdOut.ReadLine()
		strText = Replace(strtext, vbTab, "")
		Do Until InStr(strtext, "  ") = 0
			strText = Replace (strtext, "  ", " ")
		If InStr(strText, "ID File Clients Size Status Enabled Extended Privileges") > 0 OR _
			InStr(strText, "ommiORB") > 0 OR _
			InStr(strText, "IP Address Is invalid Or inaccessible") > 0 OR _
			Left(strtext, 2) = "ID" Then
			' do nothing
			Redim temparray(0)
			tempFile = Split(strtext, " ")
			status = LCase(tempFile(4))
			If status = "normal" Then
				tempCount = tempCount + 1
				Redim Preserve tempArray(tempCount)
				tempArray(tempCount - 1) = tempFile(1) & ".fp7"
			End If
		End If
	getCurrentFiles = tempArray

End Function

  • 4

#396266 No records found = 401 = Filemaker script error

Posted by dsghs on 25 September 2012 - 04:34 PM

This is kind of janky, but you have to insert in a script step that guarantees no error code thrown (like "Show All Records") and then exit the script using the "Exit Script" step.


If Get(lastError) > 0
  action for failed find
  Show All Records
  Exit Script
  action for successful find
End If

If you have multiple "Perform Find"s, make sure you add the "If Get(lastError) > 0" right after the Perform Find and then "Show All Records" and "Exit Script" steps after your other script steps but before the "End If" or "Else" script step.

This suppresses the error in the schedule section of FMS
  • 4

#392001 "Strongest" way to pass multiple parameters.

Posted by jbante on 06 July 2012 - 06:25 AM

The two main schools of thought for passing multiple script parameters are return-delimited values and name-value pairs — the choice is a matter of taste, whether you prefer array or dictionary data structures. Both approaches have solutions for dealing with delimiters in the data. For return-delimited values, you can use the Quote function to escape return characters, and Evaluate to extract the original value:

Quote ( "parameter 1") & ¶ & Quote ( "parameter 2¶line 2" )

will give you the parameter:

"parameter 1"
"parameter 2¶line 2"

and you can retrieve the parameters:

Evaluate ( GetValue ( Get ( ScriptParameter ) ; 2 ) )

with the result:

parameter 2
line 2

Every name-value pair approach worth using has it's own approach for escaping delimiters. In my own opinion, XML-style syntax is unnecessarily verbose. My personal preference when working with name-value pairs these days is "FSON" syntax (think "FileMaker-native JSON"), which is where the parameters are formatted according to the variable declaration syntax of a Let function:

$parameter1 = "value 1";
$parameter2 = "value 2¶line2";

I only consider name-value pair functions practical when the actual syntax is abstracted away with custom functions. Once you do that, the mechanics of working with the different types should be interchangeable, such as any name-value pair function set that matches this standard. As long as you have a function to define a name-value pair in a parameter (# ( name ; value)) and another function to pull specific values back out again (#Get ( parameters ; name )), it works, and all variations should behave the same way. Any other supporting functions are purely for convenience, and probably can be re-implemented for whatever representation syntax you want. So I'd write:

# ( "parameter1" ; "value 1" ) & # ( "parameter2" ; "value 2¶line 2" )


#Get ( Get ( ScriptParameter ) ; "parameter2" )

I only have 2 requirements for any parameter-passing syntax: 1. It can encode it's own delimiter syntax as data in a parameter, and therefore any text value (already mentioned in this thread), and 2. it can arbitrarily nest parameters, i.e., I can include multiple sub-parameters within a single parameter. The requirements tend to work hand-in-hand with each other. If I can do those two things, I can construct everything else I will ever need within that framework.
  • 4

#382527 Conditional format drop-down calendar?

Posted by LaRetta on 14 February 2012 - 11:17 AM

Hi Charity,

We all deal with wanting to eliminate the display of buttons, checkboxes, drop-down calendars and such on that last row when Allow Creation is in effect. Instead of having to eliminate the objects individually, you can accomplish it all with conditional formatting AND make it clear to your User that they click the last row to add a new record. Here is how:
  • Create a text box with the words [ Add new record here ... ]
  • Make the background transparent. Color of text does not matter
  • Resize the text box to same size as single portal row
  • Format the text box as follows (using conditional formatting)
  • First entry: Formula = not IsEmpty ( the primary key from the portal table occurrence ). Then below select ‘more formatting’ and set the font size to custom and 500.
  • Second entry: Formula = IsEmpty ( the primary key from the portal table occurrence ). And below set the text to white and the background to black as example. You can set it anything you wish.
Select this text box and Arrange > Bring to Front and place it over your top portal row. This one text box hides checkboxes, drop-down calendars, buttons, lines on empty fields, etc only on the empty row and also provides a clean row in which to provide your message.

I use it on all Allow Creation portals - just by changing the ID referenced within the conditional format portion.
  • 4

#431825 Data Analysis Intro

Posted by LaRetta on 10 December 2014 - 08:49 AM

Fascinating!!  Prior to identifying the tools, the questions must be asked ... not the question of whether to analyse our business data in this broad sense but what do we want to achieve from the analysis.  For example, many years ago, I migrated 10 years of complete business data from a Wholesaler in to a new FileMaker solution which integrated accounting, inventory, sales - the entire business.  As I viewed the data, there appeared to be patterns and spikes in sales and I thought it was because of full moon.


I wondered if Buyers contacted our Wholesaler company in patterns.  Why would I care?  Because if we could predict a pattern of contact, we could predict sufficient sales staffing and even contact those Buyers who didn't call us  ... thinking they probably wanted to call us (like all other Buyers) but were too busy.  Maybe the sales calls to these chains during low periods were less fruitful ... we could change our methods accordingly.


So the questions I asked (and finally COULD ask because we had gathered the data) were:

  • Gender: Is same sex (Buyer to Sales Rep) more productive or the reverse?
  • Who contacts first ... if we call them or wait for them to call us?
  • Time of day, day of week, day of month?
  • ... and my favourite ... do sales spike during a full moon?

Back then, there were no databanks on the web of surveys and studies like there is today.  Neither did I have college background so I had no Statistics or analytical skills.  But even winging it, we DID find patterns and sales increased by 20%.  The full moon comparison showed a negligible spike but the biggest percentages were day of month and day of week.  :-)


I look forward to this discussion because the power of data modelling is underestimated.  Thank you for opening this discussion (and to Stephen for opening this forum)!  It is a subject which has always intrigued me and I look forward to learning from everyone about tools, calculations or methods to take full advantage of our data.

  • 3

#413680 ExecuteSQL Custom Function

Posted by Wim Decorte on 10 November 2013 - 09:22 AM

FileMaker Server will try to execute the SQL query on the server so you will only get the result.  If that result is a record set of thousands of records then obviously that is what FMS will have to send you.


There is one exception to FMS doing the query for you: if you have an open record in your session for the target table then FMS will send you the whole table so that your client can perform the query including the results of your open record.  That is usually not a problem unless there are more than say 10,000 records in the target table.  And the wait becomes exponentially longer the more records in the target table.


An example:


Table with 1,000,000 records.  You construct a SQL query that results in 1 record.  You have no open records in the target table (if other people have open records, that does not matter) --> FMS will do the query and return you the data for the one record.  And it will be fast


Table with 1,000,000 records.  You construct a SQL query that results in 1 record.  You DO have open records in the target table (if other people have open records, that does not matter) --> FMS will send you the data for ALL 1,000,000 records and your local copy of FMS will execute the SQL query.  It will be very slow.

  • 3

#408355 Location/size of Mac dock & Windows status bars?

Posted by Vaughan on 07 July 2013 - 05:04 PM

Ultimately all you can do is design for the default sizes and positions of windows and OS widgets, or if you're keen, take into account the window size when the dock/taskbar is on the side rather than the bottom.


If I want to make my task bar half the height of the window, there is nothing you (as developer) can do about it.


Decide what the *smallest* screen your solution will support. For me it's Apple Macbook Pro 13 inch 1280 by 800. Make a test file with a layout and size this so the window just fits without the scroll bars appearing. Now move the dock to the side and resize the width of the window so it still fits.


Load this same file onto a machine running Windows 7 (and/or 8) and resize the layout so it fits. Only make a dimension smaller, not larger.


The resulting layout is now cross-platform.

  • 3

#395884 duplication of data, script variables, and lookups?

Posted by LaRetta on 17 September 2012 - 09:41 AM

Another consideration is whether you need to move the data at all; eliminating redundant data is the usual goal. Since you mentioned lookups, it suggests that the tables are already related. So here are some additional considerations if the tables are related or you want them to be:

1. Cross place fields - simply place the parent fields on the child layout; no need to duplicate. This works well if you want the data to change if the parent data changes and if the parent is the 'one' side.

2. Copy only the ID to a variable, go to the new table ( behind a Freeze Window ) create new record and set the parent ID in the child with the variable, commit the record, then set any other fields directly as Set Field [ child::parentAddress ; parent::Address]. This works well when you need to plant data and have it remain as it was at the time (you want parent address at the time of shipping the order and not have it change if later their address changes). The only time I would write all data to variables is if the tables were unrelated.

"I am under the impression that a complete record of a transaction should contain all of the data which pertains to it, not relate to data in a different table."

I would suggest the opposite ... data should be displayed through relationship unless the data might change and it's value at the time must be preserved. Shipping would fall into this category for customer address, or Order LineItem with Product Price ... each situation and field should be considered individually.
  • 3

#387176 interface check

Posted by Vaughan on 19 April 2012 - 02:06 AM

No: do not attach your database. No.

Yes: explain what you want to do. Yes.

Explain with words what you want to do. Explain the problem, not how you think it should be solved.

DO NOT TALK ABOUT FIELDS OR TABLES OR SCRIPTS. These are implementation details and are part of the SOLUTION. We are not up to the solution yet we are defining the PROBLEM.

Talk about: patients, diagnoses, conditions, appointments, drugs, measurements, tests, results, invoices, payments, hospitals, doctors, pathology labs, prescriptions... whatever is part of the PROBLEM you are trying to solve.

Explain with words.

Do not send me a PM. Post only to the Forums. I do not respond to PMs.
  • 3

#418661 Auto-Enter Get( CurrentHostTimestamp)

Posted by comment on 24 February 2014 - 01:04 PM

One more thought has occurred to me: what would happen if you changed your host's location?


Why am I bringing this up? To illustrate that Get (CurrentHostTimestamp) is NOT an attribute of a transaction. A transaction recorded in New York with the timestamp of the server in Sydney becomes "out of sync" with a later transaction recorded in New York with the timestamp of the server in  Los Angeles. In order to get everything back on the same timeline, you would need to adjust the old transactions' recorded timestamps - and that's a clear sign of poor structure.


Recording both the local timestamp and the location should provide all there is to know about when a transaction took place. And if you also record the UTC, you won't have to figure out when a particular location switched to or from daylight saving time.

  • 3

FMForum Advertisers