Jump to content

Dimitrios Fkiaras

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Dimitrios Fkiaras

  • Rank
    member
  • Birthday 07/30/1972

Profile Information

  • Gender
    Male
  • Location
    Cyprus

Recent Profile Visitors

825 profile views
  1. I want to conditionally format the items (btns, fields) in the active row of the master portal. Thus my formula is : Get (ActivePortalRow) = Get (RecordNumber). This works ok, but when I click outside the portal, the formula no longer validates correctly. (however, in the Data Viewer, the Get(ActivePortalRow)=Get(RecordNumber). I am using FM17 on Windows 7 machine.
  2. Sorry for continuing this thread. I haven't got any success in showing a local .html file thru WebViewer I entered the absolute path, as that was calculated by the example file in post #2 (for a MAC computer) The webviewer seems to find the file but give me a message that a suitable application was not found to open the file What is wrong? ** UPDATE ** Solved : I had a problem with slashes "/" "file://Macintosh HD/Users/JohnDoe/Desktop/Folder/File.html" correct format
  3. Dimitrios Fkiaras

    General structure of Inventory and Assets management

    Any help.... ?
  4. Dimitrios Fkiaras

    Software and Hardware Inventory Database

    Well, I am currently working to accomplish something similar, so although I am quite novice I would like to express my thoughts. I think that its very good you have a clear view of what info you wish to see. Also I think that it is important to imagine how you would like to see all these data and with what interaction by the user. For example : Maybe you see all computers in a portal with 3 columns [Name, Hardware Serial, Building] then you click on a computer and then you sees another portal which has the columns [SoftwareTitle, Lisence, Verion, PO, Date] Its important to have an idea about the user interface and data presentation, because sometimes you have to create new Table Occurences in the Graph just to create the appropriate "paths" between data to present them in the way you imagine (this is vital if you plan to use portals). I don't know if I am correct but I think that every time you wish to display in the same layout lists of data that are related you can't avoid portals. Another trick I learned lately is this : If you want to present a portal with all the computers you can't base the layout on any of the related tables because it will show only related records to (P.O, Locations etc). So you can created a table with just one record (lets call it VIEWER TABLE) and relate that table primary key to a global field in the ASSETS table. Thus all ASSETS will be related to the one and only record in VIEWER TABLE. So when you make a layout based on VIEWER table and a portal based on ASSETS you will see all ASSETS. By filtering the portal by the Asset Type you can get is to show only the Computers Glad if I helped Dimitris
  5. Hi, In an Asset managment solution, do I absolutely need these tables: Asset (e.g. HP Photosmart 102b)------< Individual Assets (e.g. HP Photosmart 102b | s/n:1234567890)---------< Transaction Items >------------Transactions ? Currently I don't have an Individual Assets table and all Individual Assets are created in Transaction Items table and a Serial number is assigned to them there. When I sign out an Asset, I create a new Transaction and when it is returned, I flag the Transaction as VOID. I know I have that Asset at hand if it appears only ONCE in my CURRENT Transactions. (VOID Transactions are excluded via self join) If it appears only once it means that I have only one relative Transaction the one that I created when I first received the item). If I have two, it means that I reveived it and then made another Transaction (signed it out). Is that a correct approach? What are possible pitfalls? I know for sure that this approach is used when handling Inventory, I don't know about assets but if feels a bit odd having this structure of mine... I am a bit confused about it.... Thanks Dimitris
  6. Dimitrios Fkiaras

    Self join Relationship or New Table?

    What are the things to have in mind if implementing the supertype/subtype model? I hope this is not a too general question
  7. Dimitrios Fkiaras

    Self join Relationship or New Table?

    Thanks!
  8. Dimitrios Fkiaras

    Self join Relationship or New Table?

    Hello, In my solution, I have a "Personell" table which includes about 400 records. Personell is distinguished, according to its specialty to : mechanic electrician driver Some fields in this table hold attributes that are common to all records(Personell) like: DOB Address Phone number Email et.c. On the other hand, each specialty has its own unique attributes. For example "drivers" have: licence ID licence type Total hours behind wheel et.c. Should I put the fields that hold specialty-unique attributes, to my main table ? OR Put them on a related table that holds only the _pk of each Person , and make a script to populate the new table each time I have a new entry on the old? Thanks!
  9. Dimitrios Fkiaras

    Seeing the big picture

    Hello and thank you all, This is my second question in this forum. I am novice in FM and I work for a medium-sized aviation organisation. (my job there hasn't anything to do with FM). I have a vision of creating a database to hold all data used by this organisation. Our organisation has many specialised departments. For example: a. Personell dpt b. Training dpt c. Pilots dpt d. Technician dpt e. Logistics dpt and so on..... So far I have build two databases to keep track of Aircraft spare parts and Flight records. How does one starts designing such a large database, so that I wont have shortcomings with my ERD- Later? Bear in mind that I cannot collect all info about the organisations need and then start programming, and I want to deploy some solutions for certain dpts a.s.a.p. I have a picture in my mind about designing a piece of a puzzle each time and when ready adding it to the existing solution. I have read about the Data Separation Model and it seems a good idea to keep all data separated from interface. I know its a large subject that I am asking about, I would appreciate any advice or any links to good training sources, preferably low cost or free Thank you!
  10. Dimitrios Fkiaras

    One-to-Many Relationship with OR operator?

  11. Dimitrios Fkiaras

    One-to-Many Relationship with OR operator?

    Hello friends! I am building an application for a flight instructor who wants to keep track of the organisation flights. The database has a table named "PILOTS" (one) and a table named "FLIGHTS". The problem i face is as follows: Any flight has a crew consisted of CAPTAIN and CO-PILOT. Any pilot for "PILOTS" table can sit in any of the two positions depending on the certain flight. How do i set a relationship, so that I can see all the flights from the perspective of one pilot (basically i want the matchfield to be FLIGHTS::CAPTAIN or FLIGHTS::CO-PILOT) Thanks!
×

Important Information

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