
digidiva
Members-
Posts
20 -
Joined
-
Last visited
Everything posted by digidiva
-
I resolved this problem successfully. It had nothing to do with the relationships..
-
I have an appt program that was recently upgraded from FMP6 to FMP7. Since the upgrade, the calculation of Initial and Follow-up appt times does not work. in FMP6, whenever an Initial or Follow-up appointment is scheduled, FileMaker is creating an entry in either the Iappointments or Fappointments table. Part of the data in each of these records is the InitialDate or FollowDate, along with the PatientRecord number. IN FMP7, the unit of this program that seems to be failing is the MatchFieldForShowInfo.c field. A patient whose record# is “10-3157” and schedules an appointment on “08-09-2005” should have a resulting MatchFieldForShowInfo.c field calculated to “103157892005”. This information is used to connect a relationship with a similarly calculated field in the DrGood.fp7 database If everything worked as it should in FMP7, then a ‘Find’ operation (using the Find_script) would find all related records in the Iappointments and Fappointments databases, toggle over to display all records matching the request, and display related information (based on the matching relationship of the MatchFieldForShowInfo.c field). Unfortunately the calculation in the database (GetAsNumber(RecordNumber) & GetAsNumber(gFindDate.g) works unreliably, creating unpredictable results, thereby nullifying the possibility of a match, or worse, generating an unexpected match. Someone has advised the following: "To solve the problem will require replacing the core of the relationship underpinnings in your system" is this true? how would it be done? is there a more reasonable solution? is there a way to easily fix this? any ideas? Thank you.
-
I have looked at your second example and am not sure about it. I am not sure why you need to mark the field to create the record. I Think it is beyond my mind right now. I have attached an example file of the problem I am trying to resolve in the simplest form. Perhaps you can reveiw this and instruct me further according to this example. thank you for taking a look. helpSample.zip
-
The other option, that is not as expensive as purchasing the DEV version for the runtimme (which is really the best solution), is to simply share your database using the webpublishing feature built into the program. You can protect your data with the password option and only those authorized will be able to view and use the content. And, whenever you update your database, the changes appear automatically. You will need to decide what makes the best sense for what you are doing.
-
Hi and thank you for your reply. the solution works nicely for single dates. what i need based on your example is this: The initial appt date does not change. There is only one. The followup appts do change, and, the history of the followups needs to be kept. what i have in the DBFile Followup is a PORTAL that keeps the followup appt history up to 15 appts, that are sorted by most recent at the top. that most recent appt is displayed on the mainAppt DB The data entry for both the InitialAppt and the FollowAppt is done in the mainAppt DB So, what i think i am doing is entering data in mainAppt and having that data stored in intialAppt DB and FollowupAppt DB, then I am entering a layout in MainDb and finding the appt dates, times and type from intialDB and FollowupDB and having that information displayed in a columnar report as you have done in your elegant example. can your example be expanded to do that? Thank you.
-
Hi. I am doing a single date search, not a range. I would like to search 2 fields in 2 different related databases and have the single result placed in the main data base. restated: I would like to enter a single date and search for all "followup appts" and all "initial appts" for the search date and have that information displayed on the layout "daily schedule", along with the corresponding time and appt type (initial or followup) the structure: DB1= daily schedule DB2=followup appts DB3=initial appts the appt type is a global field in both DB2 and DB3 where I =Initial and F=Followup Currently, DB2 and DB3 hold the appt information. DB1 is where that information is entered and displayed on layouts with portals and relationships. DB1 is where the search criteria will be entered and displayed. I have all the elements, I just do not know how to stitch it all together. Thank you.
-
Why would a global field be used (gFindDate) when global fields cannot be used for finding data?
-
C = A + B script needs help
digidiva replied to digidiva's topic in Script Workspace and Script Triggers
More information, you got it...please see my post "Multiple Finds: Portals and fields" under Finding and Searching.... the information from both A and B need to be displayed. -
I need to execute a script that does this: Enter search criteria in field C, have the find look in field A and field B for the results, have the results posted as a columnar report in Field C WHERE: Field A and B are a date fields, result C is a date field WHERE: Field A is in main database, Field B is in another database, result Field C is in main database If needed, the search criteria can be entered into new field D, where results from A and B are displayed in C In all instances, only a single date will be searched, not a range. The results from both field A and Field B MUST be displayed in field C Thank you.
-
Yes, I did create the relationship correctly. I suppose I need to revisit my problem. What I want to do seems so simple. Search A and B place results C
-
the search criteria will ALWAYS be a SINGLE DATE, not a range. I will implement your suggestion and let you know my results. thank you for your assistance with my speghetti dinner!!
-
I tried it an could not make it work. The global field just showed whatever date I typed...the find did not find any thing. Am I missing something here? enter search date xx/xx/xx, look in 2 places (field 1 in main database, field 2 in either: main database portal or different related database), show results in columnar report...
-
the problem restated: I have a relational database. One of the layouts in the MAIN DB is called DailySch. On this layout I need to enter ONE search date in ONE search field, ex 10/6/01, then, I need that search date to look in TWO places for the results: the first place is in the MAIN DB in a field called "initialAppt", the second place is in the MAIN DB in a field called "recentAppt", where "recentAppt" is already in a Portal from the related database "FAppts"...the Portal contains fields ::FollowDate ::FollowTime, this layout autosorts for the most recent occurance to appear at the top. NOTE: the related database Fappts stores all of the occurances of RecentApps, RecentTime, etc... I would like to search the database to have ALL occurances of a single search date from 2 sources appear in a single columnar report.In that columnar report, I need to have displayed, based on the search criteria Date of appt, time of appt, Fname, Lname, Rvisit I want to hit 2 birds with one stone, and both birds have the same color, but are in 2 different bird cages. Since the end user needs this ASAP (As Simple As Possible), entering data into one field to get information from 2 sources is the easiest. I hope this additional information is clarifing. Again, thank you for your input and solutions.
-
FMP 5.5 is out and available. so stop waiting impatiently and jump into action! The questions for you are: 1. Are you using the web companion plug-in OR the TCP remote access plugin?...2. Are you using a FMP hosting service, or are you hosting yourself? Using the TCP remote access plug in allows the exact layout to be printed as designed, the web companion is an html based display and prints the layouts differently than designed. Access is not a problem with either, however, if you want security, the passwords help. AND by using the TCP remote access, you can control the security by giving the IP address to only those who need access...
-
I need to search 2 sources for a single found set: source one is a field called : initialappttime, the second source is a field in a related database called followupapptime. I need the search result of both of these sources to appear in one place, layout: dailyschedule, in a columnar report. I am making speghetti of my script. Thank you for your assistance.
-
Most recent data to specific fields
digidiva replied to LiveOak's topic in Script Workspace and Script Triggers
Okay, I implemented what you suggested. Ignore previous post. Question: I have 2 layouts in the Patients file. One layout lists the entire followup visit history for a patient, Followups, the other is the patientData layout, where the appointments are recorded and the most recent displayed. What I would now like to do is this: on the patientData layout, where only the MOST RECENT followup appt appears, I would like to be able to do the entry into that field on the patientData layout of the followup appt, have that information goto the Appointments Database, and appear collectively in Patients layout:Followups: I thank you for your solution and assistance. [ October 01, 2001: Message edited by: digidiva ] -
Most recent data to specific fields
digidiva replied to LiveOak's topic in Script Workspace and Script Triggers
I am looking into what you are suggesting. Here is one more piece of information that might have been missed: each patients Follow-up visit (fields FA1..FA15) needs to be stored for that patient. That is why I have chosen 15 fields. To allow for at least 15 followup visits (reality is about 3 visits per patient)... -
Most recent data to specific fields
digidiva replied to LiveOak's topic in Script Workspace and Script Triggers
the goal: to have the most recent (date of appt) (time of appt) (reason for visit) information appear from the (follup appt) layout to the main (patient info) layout. Currently, the (follup appt) layout has fields (FA1..F15) follow-up date, (TA1...TA15) follow-up time, and (RV1..RV2) (reason for visit), I would like the MOST RECENT of each event, based on the fields (FA1..F15) to be placed on the layout (patient info) automatically. When the most recent appointment date changes, then the (patient info) layout fields will update automatically with the most recent information from the fields (FA1...F15), with the corresponding information from (TA1...TA15) and (RV1...RV2). thank you for your input. -
if you are trying to pull inventory information from several different stores (databases), then why dont you just create a look-up/relationship page that queries all databases and pulls the requested information into that search page? the question is are you storing all of the databases locally or not. you can also create one huge database and have each item associated with a particular store. Then of course, you need to ask, in either instance, how doest the database get maintained? you can also create a webbased store shopping cart that has auto inventory control...so many ways, so little time...
-
agree with the previous.using OS 9.2 and fmp 5.5, no problems, no crashes. The web companion works really well, though not with Airporter distributed IPs...and that is not a FMP issue.