9 posts in this topic
By Cynthia Heyman
I'm brand new to Filemaker. I'm trying to figure out how to make a left menu area that will appear in all of my layouts for navigation purposes. To switch from layout to layout easily for the user when my application goes live.
I'm not even sure if this is possible, but from what I'm reading, it looks like it may not be.
Would there be a way to split a layout into two vertical sections, the left one being the menu (which I can duplicate on every layout if necessary, though that would be a pain), and the right area where the actual program interactions appear?
I'm so new that I'm not even what the correct terminology is.
I am not sure if this is a tip, or if it is already known.
Anyway it has a practical value for me so I thought I post it.
Sometimes I need to present data in a layout with several sub-summary parts and usually no body parts
I find it good interface, to give the user the ability to click on the only visible sub-summary part and reveal the next part in the hierarchy, and so on...
Thus expanding and collapsing the list by clicking on the headers.
From what I read in the forums the standard technique for this is to have a global variable to store whether part X is expanded or not.
I don't like that method very much so I thought of an alternative.
Layout Example Structure
Sub-Summary Part1 (based on COUNTRIES::Name)
Sub-Summary Part2 (based on COUNTRIES::CityID)
Sub-Summary Part3 (based on CITIES::SalesmanID)
To the right of the sub-summary part, just off screen we put an instance of the field we are sub-summarizing by.
For example, inline with sub-summary Part1 we put an instance of the field COUNTRIES::Name and we name the Object as "Part1"
Now if the sub-summary part is visible using the following :
GetLayoutObjectAttribute ( "Part1";"source" ) will give us "COUNTRIES::NAME"
or if the sub-summary part is not visible will give us error 102 (Field is missing)
By looping with a $counter variable through all sub-summary parts (1....n)
we can get a list of the visible sub-summary parts (the fields they are based on)
Then we can use this information to sort the records anyway we want to.
I think it would be nice if someone thought a way to have the list sorted in the way the parts are presented.
I have a number of scripts that have worked perfectly for years in previous versions of FileMaker, however in FMP 15 they causse FM to crash. They only way I have found to avoid the crash is to use the debugger and to use the "step into" button. That of course is a very cumbersome workaround. You can see one of the culprits below. Anyone have any ideas what's wrong here?
I recently moved my Filemaker databases to a new Windows server. And since then, I’m having sporadic “Database Server process has terminated abnormally” Error 701. This is accompanied in the Windows event logs with application error 1000, and these are the details:
Faulting application name: fmserver.exe, version: 126.96.36.1998, time stamp: 0x58124553
Faulting module name: ntdll.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000374
Fault offset: 0x00000000000f1b70
Faulting process id: 0x624
Faulting application start time: 0x01d2a8b983d812e3
Faulting application path: C:\Program Files\FileMaker\FileMaker Server\Database Server\fmserver.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 2fea4014-160e-11e7-80c2-109836ac1fba
Faulting package full name:
Faulting package-relative application ID:
This did not happen on the older Windows Server, which was 2008. The new server is 2012 R2 Standard
It first occurred on the first day I starting using the databases on the new server. So updated FM Server 15 to latest (15.3). I then performed all available Windows updates, updated Java. Then a few days elapsed before Filemaker failed again, with exact same errors.
So I performed a recover on the databases within Filemaker, just to check. All fine. I also downgraded FM Server to version 14 to eliminate FM Server 15 as an issue. After downgrading to 14 we had 6 days then before it failed. But last night it went again with same errors.
It seems to occur when a scheduled Filemaker script is being run on the server. But oddly, when the server is quiet, ie. After 18:00 when people have logged off and gone home, or at lunch break. The Filemaker scripts are run every 30 mins during office hours, so run many many times over the days between failures with success, and did so for years before I moved to new server.
When the 701 error occurs, I’m forced to reboot the server. It doesn’t auto restart the process after failure.
I would be incredibly grateful for any advice on this. Anyone aware of issues similar?