Jump to content

Thumper87

Members
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Thumper87

  • Rank
    novice

Profile Information

  • Gender
    Not Telling
  1. I have created a self contained copy several times with several databases, and i was under the impression that all images store externally get embedded into the backup so when i import the file the images get placed back into the program. but every time i import the photos dont show up.
  2. I have a runtime created, hundreds of users have it, since i upgraded to FM12 pro adv i now changed all my container fields to use external open storage, when i make a backup of my database either copy of current file or a self contained single file, i still cant import the data using my import script (worked very well in fm11) to import all the records, i always get different results... sometimes no records are imported, sometimes records are but no imaged get imported, results always vary. what is everyone doing to backup the database from a runtime and restoring the data properly?
  3. Ok so with my filemaker database ready to be transformed into a exe runtime, i have several questions. I been having a lot of problems using software compilers like inno setup and exeshield, when i used either of these my runtime wouldnt open after...this is why im thinking of distrubuting the runtime without the installer a nice simple way, and i got brian dunnings easy encryption instead of using exeshield... 1.) after the .exe is created can i just give that to my users to use the program, or do i need to include all the folders and additional files filemaker provides with the runtim
  4. I am not sure if this is possible, but i have my database that i would like to have a button called "import" which would import the records through script step im guessing, grabbing the records from a complete different database file, its a .USR file. the fields are all similar between the two databases but named very differently, users importing records from the foreign database will more then likely not like having to match all the fields up between both databases to import their records, seeing as the users who will have this older database will only be importing into my new database the ma
  5. I did a quick database for what i want to achieve above, made a table called Reptiles with the above fields, and then duplicated that occurence for the sire and another for the dame, i related the fields like so: Reptiles::ReptileSire -- = -- Reptiles Occurence Sire::ReptileTagCode Reptiles::ReptileDame -- = -- Reptiles Occurence Dame::ReptileTagCode it displayed the sire and dames info properly, and i can just repeat my steps buy creating occurences for for the sires and dames up to 5 generations, but thats gonna be alot of table occurences and im wondering if this is gonna be rid
  6. Ok, so i have a table called Reptiles and fields for it: ReptileID ReptileCode ReptileSex ReptileMorph ReptileSire ReptileDame ECT... i need to setup a family tree, showing 5 generations,the reptilesire and reptiledame fields record the same data that would be inputed into the ReptilCode field, so they show the ReptileCode for sire and dame. In the image attached you can see that the subject is the record being browsed, and the (ReptileCode) for the sire and dame is showing, but the other fields which just show the same data from the subject because i dont have fields setup t
  7. Thank you Laretta, that really helps me from getting confused with the field names in my tables, i created the above relationship im having some troubles with it, im gonna play around with it tonight and see if i can get things working, ill post my results back here.
  8. I have a .USR file of another database that was created in filemaker, i can open the file in filemaker and use it, but its locked down, i was wondering if its possible to export the records from this database and import them into another database that isnt locked ?
  9. ok so i have a couple tables (Reptiles , Medical) i want to find the best way to relate the medical records to the reptiles, im assuming this is a one to many seeing as one reptile can have many reptile records and each medical record can only be assigned to one reptile. Please note that in the reptiles table the field called Reptile_ID is not a "ID" field like Record_ID, its more of a "Name" field but since breeders dont use names we use ID's (EX: M.PJ.3.34.11) I had a relationship once set up by relating Medical::Reptile ------ = ------Reptiles::Record_ID it was wo
  10. Absolutely perfect!, every works so great, Thank you so much for all this! i know it wasn't easy lol
  11. each reptile can only have one morph assigned to it....each morph could have several related reptiles, MEANING i could and do have 3 Pastel ball pythons and 6 Spider Ball Pythons thats not right actually, its the other way around, you can have many reptiles associated with a single morph, however you can have many Genetics (Basic Morphs) associated with a single Morph .
  12. I would set up a relationship but that's where im mostly lost unfortunately
  13. Ok if sammy the snake is Clown Spider then the morph that is related to sammy is "Clown Spider" and the genetics to that morph are Clown and Spider so yes each reptile record can only have ONE morph value, but that morph value is broken down into another field or portal to show "Spider" and "Clown" http://www.worldofballpythons.com/morphs/clown-spider/
  14. hmm OK ill try and explain this better lol believe me i know how confusing it is, when i first got into breeding the genetics had me so overwhelmed at first. First of all i need to clarify a change of the word Alleles to use the word genetic instead, i realized i had that set up wrong, so i have a table called "Reptiles" to manage hundreds of ball pythons (or other reptiles) there are thousands of different morphs specifically for ball pythons, see http://www.worldofballpythons.com/morphs/ however there are different morph names for Boa Constrictors and different morph names f
×
×
  • Create New...

Important Information

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