Jump to content

Hap

Members
  • Posts

    11
  • Joined

  • Last visited

Hap's Achievements

Apprentice

Apprentice (3/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. I have a fairly complex database that occasionally needs to import data from an Excel spreadsheet. The import requries pretty heavy processing and a very large number of calculation fields. So I decided to put all the import processing in separate filemaker files that would only be opened if an import was attempted. The import file processes all the data successfully and exports to a filemaker file for temporary purposes until the main database file can import it. Works great except for one problem: any time after the first import, the exported data is ADDED to the temp files (overwrite was selected when adding the file to the export script), therefore I endup with way too many records on import. I attempted to add scripts to the temp files to allow deletion of records after the import. However on the next export - the scripts are erased, but the data added. Happens with all file formats I have tried. Is there no way to clear a temporary file?
  2. So I got done sooner than expected. Note this DB may have some left over funtionality of the larger database it was extracted from, so everything may not work. However, the basics work do as does the RTF export. Selecting the RTF button will automatically dump to an test.rtf file in the same directory as the database. For this to work, the rtf_extend2.xslt file has to also be in the same directory as the database. The database is completely unprotected so you should be able to see how I did part of the RTF formatting in the DB and part in the xslt file. I did part in the DB for easier adjustment on table parameters, plus I never could figure out more than one related field on the same line (in xslt) without combining them in FM. I know it can be done, but never could find a good example and ran out of time. The RTF Pocket Guide from O'Reilly was very helpful in developing this format along with the RTF Spec from Microsoft. Note that except for the tables, the output file doesn't have a lot of formatting. Most of the [H#] indicaters are where I would take the file into Word and do a replace all with the appropriate Heading level style - takes about 2 minutes with an 800 page document. Complex style formatting in RTF is flakey and I prefer the search and replace method in word using keys. Sample.zip
  3. Brudderman, just going to let you know that my "sample" is delayed a bit. Had to unexpectedly work most of the weekend. I'm about 70% of the way there. I thought it would be easy to cut my database down to a simple example. I didn't realize it had grown to over 66 layouts, 34 tables, and hundreds of fields. Cutting it down to the essentials (and removing the proprietary data) was a bigger job than I expected. It would have been easier to start from scratch, however I am most of the way there now.
  4. How do I change encoding? Everywhere I see it, the option to change it is greyed out.
  5. I can't use my existing db file as it includes propietary data. I'll see if I can make sometime this weekend to make a simple example.
  6. I've got a large database that we've routinely exported to .xls format. The database opens and works fine in Excel 2000, however in Excel 2003, certain fields are replaced with question marks, everything else is the same. Everyone of the fields that has this issue uses the List() function in FM pro to get related data into one Excel row. Does anyone know what causes the difference?
  7. I can give you some hints. FM -> XML DSO Export -> XSLT -> RTF (Yes I know DSO is depreciated, but I haven't had time to go back and change) Basically you set up your FM DB to export to XML via and XSLT stylesheet that transforms the data into Microsoft's rich text format. Below is a piece of my XSLT that does this for me - I push a button and get an RTF formatted document. It's just a snippet from my XSLT file. Things get a little more complicated if you're including relational data. You can also setup FM with some of the RTF code and get nicely formatted tables. <?xml version="1.0" encoding="UTF-8"?> ENTITY tab "" ENTITY pr "par " ENTITY bold "b " ENTITY ul "ul " ENTITY it "i " ENTITY op "{" ENTITY cl "}" ]> {rtf1mac{fonttbl{f0froman Times New Roman;}{f1fswiss Arial;}}{colortbl ;red255green255blue255;red153green102blue51;red255green255blue204;}titlepg {headerqr{field{*{ BMC4I IPT }}{fldrslt }}{par}} &op; [H2]Tests&cl;&pr; &op;[H3] &cl;&pr; &op; [H4]Objectives &cl;&pr; &pr; &op; [H5]Critical/Non-Critical Task &cl;&pr; &pr; {footer qr - page {field{*fldinst { PAGE }}{fldrslt }}{par }}} }
  8. I have a large number of records that I'm trying to update using FM8 Advanced "Update matching records in found set" with the add new records option. The matching field is a unique ID number in both the existing database and the records to be imported. However when I finish importing, many of the records have been updated with data from different records in different fields. In other words record A, field 1 will be updated from imported record A, field 1, but field 2 will be updated from Record C. As far as I can tell , it is a completely random shuffle. Happens whether I import directly from another Filemaker database, Excel file and happens on both XP and OS X. Comments/suggestions.
  9. I have a member directory that works fine except the format the customer wants printed. Basically they want the following: Family Name FirstName1 Data MoreData FirstName2 Data MoreData Family Name 2 etc... Right now I a sub-summary based on the Family name. Works great, except that sometimes a set starts near the bottom of one page and flows to the next. Customer does not like as the Family Name gets separated from some of the members. Tried using a relationship and a portal, unfortunately the individual portal rows will not shrink based on content. Leaves a lot of white space. Again, customer does not like. Any other ideas about preventing subsummaries from breaking across pages? Thanks...
  10. Sorry, I gave up on getting a response way too soon. Came back for a different reason. However, to answer your question, I cannot post the contents of the file. Propietary data. However, I am confused by the fact the import preview box shows each record properly but the actual import is so different. Basically it imports Record 1 fine, the second record contains data from the first row of the CSV file, rows 2 and 3 are completely missing and row 4 shows up as record 3. Seems like the pattern repeats. There is a series of data in row one something like this: Document 1, Directory/Path/To/Performance/Data,Joe,1.0889,1/15/06 10:35,"Requiment text changed","MBM.343435,MBM3535" The MBM.343435 is where the second record starts - it is still part of the first CSV row. It should be noted that I don't import all of the data in the CSV file, it is a dump from a high-end requirements tool and I just import what I need to use. Thanks
  11. I'm having an issue with FM8 Advanced having an issue importing CSV. For any database created under 8, the CSV import gets hosed. Looks great in the import dialog and I can preview every record just fine, however the actual import does not match the preview. Basically the first record imports perfectly, the second record imports the wrong data (about half way through the second record) and this just ripples through the entire file. For one of hte problem imports I get 503 records when I supposed to get 963 records. This does not happen in any of my databases upgraded from FM 7 to FM 8 - they still import fine. Same issue occurs on both Windows or Mac no matter what I do in the import dialog. So far my only solution is to open the CSV file in Excel and save as a workbook. FM 8 import correctly then, but this really breaks the automated import ability in my delployed solutions. I've searched the forums and googled and not found any similiar reports. Any suggestions are welcome.
×
×
  • Create New...

Important Information

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