Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ryyno10

  • Rank
  1. "Pooled" meaning that the FM server would use resources "as needed" (depending on server workload) versus a static configuration which would "lock-in" resources regardless of server workload.
  2. Any suggestions/limitations to hosting FMS 15 in a virtualized environment? Currently, we host a 30-40 user, 10 gig FM db on a physical server, however, p to v is being suggested by others in our organization (They're also inclined to config pooled versus static resource settings which would seem to affect the manner FMS functions) Elaborating on specific VM configurations in a Windows environment would be greatly appreciated!
  3. I suppose more specifically, will the validation settings prevent the importation of unique values that aren't in the found set when the import is executed?
  4. Sorry comment, I meant to say will validtion prevent the duplication of imported records, regardless of the found set The SQL tables will not contain duplicate ID numbers, either.
  5. I'm scripting an ODBC import (Microsoft SQL Server) from a hospital information system. I'm using this infomation to construct a report containing "notes" which can be viewed/printed else where in a different FM11 file. I'm unsure as to the best way to approach importing these records and I was hoping to get some opinions on the circumstance: Background Info: I have a relational key that can be used to join imported records to existing filemaker records. I have an ODBC driver installed on each workstation in order to access the appropriate SQL tables via FM 11 ODBC import. Approach: I could import reports at the moment an employee executes/navigates to a particular report layout. I could create an SQL import with the appropriate "WHERE" clause which would reduce the import performance hit (versus importing 10000 + records each time). Question 1: With the latter approach, I'm concerned about importing duplicates. To avoid duplicates in each imported table, will validation rules prevent duplicate records from updating? For example, if I put a validation rule on a primary key field and a import is conducted while a found set is present, will this alway result in the importation of new records? Tests: I have executed scripts to import records, including validation rules as described above, and it seems to be working to fit my need (not importing duplicates, even when found sets exists). Any comments or suggestions would be greatly appreciated!!
  6. Could anyone shed some light upon how to properly test backup files? Today, one of our files crashed during production hours and I restored it with a backup file, however, I'm unsure whether my backup will eventually face the same fate. The consistency check cleared my backup but I'm not sure if that should put my mind at ease. I am currently running the most recent version of FMS 11. Thanks in advance!!
  7. I like your suggestion. Transcription could just as easily place a carriage return if the line is cut off versus splitting long paragraphs in the virtual list. Partly, i shot myself in the foot deploying a solution without thoroughly testing... lesson learned. I thought I would be able to create a script that would place a return when needed but ultimately that approach is cumbersome and would likely be difficult to make adjustments in the future. How did you determine where the red line would appear? Did you calculate total characters per page?
  8. I haven't been able to upgrade to 13 yet due to our hospital's slow transition to windows 7. Do lines still get cut off when printing large documents? I can have the typist insert the breaks but what about the previously typed letters? I have tried to calculate the number of characters per page in order to insert carriage returns, however, it seems to be an ardous work around. I'm trying to keep things simple but have yet to develop, or find, a better way to go about this...
  9. I decided to try the virtual list due to page cut-off that occurs in filemaker if the text is longer than one page (this is really looks unprofessional and often unreadable). Either the text is cut in half or the line of a document simply disappears (which is a huge problem considering this is medical information for patients with cancer). Thus, the only work around I've concluded to use is the virutal list. To be honest, everything works great except when a short paragraph is followed by a long paragraph (at which point the short paragraph appears on the first page with a large amount of white space ). here is a shot of the issue...
  10. Sorry I don't post often to this site so I'm unsure how to upload an image...
  11. For instance, if a there is a long paragraph it does not run from one page to the next... it is simply pushed onto its own page.
  12. I'm attempting to implement the virutal list technique in a database that generates patient consult letters and such. The transcriptionist transfer text from word documents, after transcribing a dictation, into a text field. This information is then electronically signed by the physician and populated in queue for faxing. After the document is e-signed it is viewable to various user groups at which time the virtual list generates a document in preview mode (for printing, viewing, etc.). However, I can't seem to find a way to "chop" paragraphs towards the bottom of the page. For example, if the first paragraph of a letter is close to 300 characters and paragraph two is closer to 1000 characters, paragraph 2 is displayed on the next page leaving a large blank space at the end of the first page. The only solution, thus far, has been to introduce another carriage return where the longer paragraphs "should" break (this will be sure to drive the transcriptionist crazy and effect production). Has anyone experienced this problem with the virtual list? I've search the web for a solution but was unsuccessful finding a solution (or direction to solve the issue). (Also, I'm working on a file to post)
  13. Although this is an old post, I had the same issue with Windows 2008 R2 (w/ FMS 11) that was left un-resolved by a previous DBA. The FMS update patch version 3 resolved this issue... If you read the "Read Me" document along with this update, take notice that a memory leak is associated with FMS hosted databases close to the size of the RAM installed on the server.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.