14 posts in this topic
My goal here is to write a database with tidier relationships than I've used in the past, so I'm intending to use discrete table occurrences of the same data. Here's the roadblock:
In layout 2_week_schedule, I have 14 portals that display a staff schedule (two weeks' worth) and can't be edited. My goal is that a logged-in administrator can click on the date field of any one of those fourteen days and go to a layout 1_day_schedule that is displaying the same information, though with more details and one day at a time.
The underlying table of each layout is the same, though the layouts are based on different TOs.
I wrote this with a script trigger in the date field in 2_week that fires a script to copy its value as date to variable $date, switch to the 1 day layout, and set the pertinent date field there to variable $date (and then commit).I don't know if it's my error, but I think of variables as being like my computer's clipboard - any value can be copied & pasted to/from. But the script fails with the message The operation could not be completed because the target is not part of a related table.
I did try a simple redundant relationship (connecting the two pertinent fields), but that was a hail Mary, and didn't do the trick anyway. Is there a better way to accomplish what I want? In short, I want administrator who's scrolling through the existing schedules to be able to look at any date where she wants to make a change, click on it, grab its contents, and be brought to a more flexible interface where its contents get inserted into a portal that will then show her the results.
This file is web-accessible, so I can post its address if it helps to see what I'm talking about.
I'm just returning to FileMaker development after years away. The last time I developed in FileMaker was... version 6!!! Wow, has a lot changed, and thank goodness it has.
I'm trying to understand FileMaker database schema design. I have a decent knowledge of normalized database forms, but the concepts of having multiple Table Occurrences, and Table Occurrence Groups, are quite foreign to me. I understand what they are on the Relationship Graph, but I don't yet understand how to plan and use them while constructing my solutions.
Can you direct me to some good tutorials on these topics? I imagine I'll need to examine more than one tutorial (and sample files) in order to truly grasp the concepts, so the more the better!
My first post here from a relative novice, so I apologize is this is a dumb question or one that has been covered many times. I'm starting to build a database for an academic department, to keep track of contact information, as well as publications, grants, applications, and other items associated with the different department members. Department members can be one of several different positions or "ranks," such as faculty (professors, associate professors, etc.), post-docs, grad students, staff etc. I also want to keep track of the relationships between these various department members, for example, which grad students "belong to" which faculty member. Ok, now my question: Should I keep everyone in one "Department Member" table that has a field denoting each member's position, or should I use a separate table for faculty, grad student's, post-doc's etc. My intuition tells me I should use one table for everybody, to avoid duplicating lots of contact fields. But if I do that, how would I relate grad students, for example, to professors? Would I create separate table occurrences of the Department Member table to use for each position (faculty, grad student, etc.), and relate those different table occurrences? Many thanks for advice.
Is the only way to change the data-source of a table occurrence, manually?
I'm working with a data separated solution that has one presentation database and 3 databases containing data. When the system was originally designed there were good reasons (at the time) to have 3 separate databases for the data. Now it no longer makes sense and is over-complicating development. I'm hoping to combine the 3 data databases into 1. But it's going to mean changing the data-source for 400+ table occurrences in the presentation database.
Hoping there is a method by which I can change them in bulk?
I found this (http://stackoverflow.com/questions/5764809/filemaker-batch-changes-to-source-of-a-table-occurrence) but I'm not experienced with AppleScript, so hoping for a Filemaker solution.
Thanks for any ideas!
p.s. or maybe it isn't worth it and I should just stick with 3 separate data databases.
I have a 45 file solution currently running on FM Server 11 Advanced that was originally built in FMPro 5-6 (by someone else). All of the External Data Source paths are set to use relative (file:filename) paths only, but the Source File listed in the TO's is using the "fmnet:/IPAddress/filename" path - in the case of one table its even "fmnet:/*/filename".
Logically it seems this would be a performance problem if the db files, which are all in a single folder on the server, are having to resolve the fmnet path rather than just using the relative path. I know the * in the path is a major no-no.
If I go to External Data Sources and add a source by navigating to the file through the Add File... > Remote selection, the file is added to Data Sources with the relative path, but the TO still has the fmnet path, so it's not just the pre-existing TO's - even the file with the * in the path comes over that way every time even though in the Open Remote dialog where I select it to add it displays the full IPAddress. So I can't just redo all the data sources.
Never seen this before and can't find anything online. I manage/develop several other solutions and the TO's all use the relative path, so this concerns me. We're currently rebuilding to take advantage of more modern features and to address performance issues we're experiencing as we grow - so I want to get this right.
If anyone knows what's going on - especially if there's a way to correct this, I'd appreciate any insight.
Files are named with an extension other than fp7
DB files are on separate HD than FM Server (still on the same machine)