Jump to content

kraftyman

Members
  • Content Count

    63
  • Joined

  • Last visited

Community Reputation

0 Neutral

About kraftyman

  • Rank
    member
  • Birthday 09/16/1969
  1. If you are using plain old Server 7 then you're out of luck... ODBC only works with Server Advanced..... and only in Windows so just hand over your wallet...
  2. I don't think you can get away without lots of fields IF you leave it all to filemaker. FMP was never designed to be a statistics tool. The easiest thing is to get the data out to an Excel worksheet and do your analysis there. If you have 22 fields, then presumably you will want a mean score with variance or standard deviation, maybe a count of valid entries as well. This means at least 3-5 summary fields per data field. ( you could have repeating fields for this, but the essential problem of multiple fields is still the same). Excel is MUCH better at this kind of statistics than FMP. The best thing in my opinion is to have the data stored in FMP, then pull it into Excel via an ODBC link. Then you can get pivot charts, the works.... For the man with only a hammer, every job looks like a nail
  3. yes, FMP seems to load the OLE object fully, but it perhapsonly when it is in an editable field. try this: go to field behaviour and uncheck "enable field to be entered" this may speed things up considerably ( it does for images) You may want to have a data input and a separate data browsing layout with scripted buttons
  4. There are no "events" at all. An "on change" event can be simulated by a calculation field and a plugin, see details databasepros.com type "Hidden Plug-ins" to see the page relating to this technique. I'm not sure if I can give you a direct link here Also have a good look at this http://filemaker.advisor.com/doc/14267 which is an excelent article on the subject of migration from Access to FMP7. There are also a few threads on this forum which address your problem directly
  5. Have you considered that maybe the trial version cannot be updated? Similar concept to XP pirate copies being unable to load service packs. Also check your zip file for errors Download accelerators often drop packets and corrupt files The MD5 hash should be dbf27ccc6e257c1065ea7638a6cd74f8 for fmd_70v2_win_updater.zip have a look on http://www.kennethballard.com/ for a decent freeware MD5 checker
  6. The information in the FM help file is actually quite good. I've used ODBC with filemaker since v5.0 and the trick for FM7 is to install the ODBC driver, which is NOT installed by default, for some bizarre reason. ( unlike revious versions) I found myself getting stuck because I was using the old driver... Once the ODBC driver is installed, then follw ithe instructions in the FMP help file, and you should be OK. Send me a message if you get stuck.
  7. Major differences runtime: cannot be networked does not share files (unless data files hosted on FM server, but need full FMP to access them anyway) does not offer full range of import/export file formats cannot modify design of anything no support from FMP - you have to do your own support FileMaker Version: Dev 7 Platform: Windows XP
  8. Something is cooking.... In Australia, FMP is offering 1.$100 cash back for ANY license bought before october 2003, including academic - that is a huge discount 2. Price for FMP Developer 6.5 has dropped from $ 1049 -1079 to $ 799 all of a sudden Why might this be? Methinks the old version is getting the big shove out the door before the new version... Someone must know something guys.
  9. You could also use the error capturing "on" for this script. Try this allow abort off set error capture on go to layout "y" enter preview mode ( pause ) print ( with dialogue) if status (current error) =1 go to layout "x" enter browse mode set error capture off allow abort on exit script end if set error capture off allow abort on Then if the user cancels an action such as printing, error code 1 is created. You could then send the user to the original layout. The only down side is that the user has to press continue, and then cancel the printing to get back to the original layout. You could also have a global field with the number of the last layout entered when that layout is left, and then when the user cancels the script, they caould be redirected to layout number whatever they were in last. You could also design a "pseudo preview" page in browse mode, "preshrunk" to fit a page, with read-only fields and a back button.
  10. You obviously use carriage returns in your felds ( bad move for compatibility) Filemaker translates every return character (ASCI code 13) into ASCI character 11. I don't know why on Earth FMPinc chose to do this, maybe this has something to do with the MAC origins. ASCI 11 does not have a symbol ( at least in windows) . (The FMP help file calls it a vertical tab, whatever that is) When this gets exported to Excel, then all you see is a box. You could emulate this with two cells in Excel. Put 11 in cell A1, then in A2 type =Char(A1) and you'll see a box. In fact the first 32 characters in ASCII do not have a symbol. I'm not sure what you could do apart from creating calculated fields to split the lines in your text fields, before exporting. Hope this helps
  11. Access to other data sources from FMP may be a breeze, but at times a rather smelly one As for your problem, I suspect you may be using the wrong driver. I am not an oracle user, but Oracle may (should) have their own (decent) ODBC driver for this purpose. This is a piece out of the readme for FMP5.5 8.3. The FileMaker Pro 5.5 installer adds an Oracle ODBC driver to the list of available drivers in the ODBC control panel. If you are already using an Oracle ODBC driver, we recommend that you remove the ODBC Oracle driver that is installed with FileMaker Pro 5.5. The FMP ODBC support is not as good as they say it is. Hope this helps
  12. It's included in the standard installation. ( for some reason, custom installations often omit the files)and remember to enable the data access companions. The FMP help files and instructions are reasonably good on this. You may get unstuck with some windows matters, but get beack to the forum to iron these out
  13. No, it simply means what it says. The value should be unique. This might be a numerical, or textual, or even a 128bit binary value ( which is used for replicating databases). If you already have some data, and tell Acess to make one of the fields the primary key, then it will check all the records and make sure the values are unique, and not do what FMP does ( FMP does not check existing records for integrity of uniqueness). IN fact it's a little more complex than that, because there are two "levels" of uniqueness. in one instance, you can simply index the data and set it not to allow duplicate values, in another instance you can also specify the "primary key" setting. The latter is used for very strict relational links that allow cascaded deletes and cascaded updates. Many to Many relationships are handled in the traditional way of having a join table. This is far less flexible than the looser FMP model, but makes it much easier to get MSaccess talking to other databases.
  14. making "relational" tables in access is a snap,you just have to decide which field your primary key is this should be a field with UNIQUE information. Then you Access is VERY strict with this. You may expose the slackness of filemaker in this regard, and have to recreate a unique number. There is a table analyzer and splitter wizard to help you make such decisions. The simplest way to get unique ID's is to add an Autonumber field, and set this as the primary key. This is the default way Access handles ID's. There are problems with it if the data is multiuser/replicated, and other things are usually employed but this is beyond the scope of an FMP forum.... and...... make your tech dude earn his pizza!
  15. Presumably ODBC is not working for you... You could automate the export to the TAB/CSV file, and then set this is up as a data source in Windows, so that Excel could automatically update a worksheet from this data
×
×
  • Create New...

Important Information

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