Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Entity–attribute–value model wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Oracle Database wikipedia , lookup
Ingres (database) wikipedia , lookup
Functional Database Model wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Relational model wikipedia , lookup
Concurrency control wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Database model wikipedia , lookup
Pacific Database Wiki Welcome to the Pacific Database Wiki This Wiki is here to help you get the most out of our excellent Database. It supplements Barry Stuart's on-line tutorial and adds information from members' correspondence on the Pacific Forum Google Group. Contents Troubleshooting Guide Getting Help Getting Started The Populator for Use with SBS-1 Getting Restarted Starting the Database - don't double-click the icon Screen Resolutions Date Formats Printouts Your Own Data Finding an Aircraft Type - Checking if the type is already in the database Requesting New Types and/or Locations to be added Updates o Downloading Updates o Updaters' Areas of Responsibility o Information for Updaters o Updating Flag o Updater Key Regular Maintenance Working with Access 2007 & 2010 Working with Windows 7 Working with Office 2013 PacReporter Integration with Planeplotter Your Problems & Solutions Limitations and Issues 1 [email protected] v2 16-9-13 Pacific Database Wiki Troubleshooting Guide The following table attempts to show the major problems and solutions encountered. The relevant section which discusses each is hyperlinked. Phase of Use Opening Database Problem Solution Database won’t open Folders need to be Trusted for Office 2007 onwards Move folders to 32-bit folders in Windows 7,8 Screen resolution not supported Database says ‘Opening’ but never actually opens Date format incorrect Two copies of database opened from double-clicking launch icon - single click only Change ‘dtset.mdb’ with previous version Delete possible extra 'dtset1.mdb' file Delete possible locked files e.g. ‘xxx.ldb’ Re-instate 'RunDataAir.mdb' from a previous backup Using Database ‘Log stats’ screen is completely blank Date format incorrect Downloading Updates Error 3027 - Cannot update. Database or object is read-only Need to unzip Update before running Creating Updates Won’t create update after upgrade to Windows 8 Need new Updater key Using Populator Popthree.mdb will spring up an error A Windows 7 error - no solution yet Using PacReporter Computer slows down Replace 3 key files with smaller versions Working with Office 2013 ‘Cannot find object Autolog’ Error Awaiting solution 2 [email protected] v2 16-9-13 Pacific Database Wiki Getting Help There are a number of sources of help available to you: This Wiki Barry Stuart's on-line tutorials The Pacific Database website at http://www.gfiapac.org Searching the Forum messages for previous discussion of your questions, at http://groups.google.com/group/pacificforum?hl=en - you will have to Login to this site Asking questions to other PacForum members by posting an email to the group at [email protected] Home If yo u are usi ng Wi nd ow s 7, yo u will fin d tha t if yo u foll ow the ab ov e ste ps, the file po [email protected] pth ree 3 v2 16-9-13 Pacific Database Wiki Getting Started The Steps The steps that you need to take to install the database are as follows: Download the database Install the database Open the database, prove it runs on the chosen PC Confirm that it worked and Ask for a key Run the key to register the Db to yourself and enable group updates to run The Files The files that you need to load the database and the drive locations that you should put them in are given below. You will be emailed a zipped file (xxx.zip) by Jim Bavin. This will contain the following files: RunDatAir.mdb dtset.mdb obs.mdb others?? the Key? You need to create a new folder on your c:\ drive called: c:\DataAir Double-click the .zip file to open it and save its files into the new folder c:\DataAir Then follow the steps below. Download and Run the .exe file Open (run) the Database and confirm for yourself it all works OK Run the Key to register the Database to yourself and enable group updates to run o Extract it from the .zip file, the suggestion will always be to the folder where you installed your database to. o Make sure that the database is closed o Run the extracted file. It will autoclose in seconds. Home If yo u are usi ng Wi nd ow s 7, yo u will [email protected] fin d tha 4 v2 16-9-13 Pacific Database Wiki The Populator for Use with SBS-1 Extra files for the Populator for use with the SBS-1 radar system: DataAirPopulator.exe ModeSlog.mdb popthree.mdb PacModeS Populator 3.0 BETA 4.exe Leon Loberman has identified the following steps: 1. 2. 3. 4. 5. 6. Build the SBS updates within the database You then run Kinetic BaseStation install – up to you which version you install – anything after 134 (I think) will require you to re-input your home location every time you start it. This must be in the default C:/Program Files/Kinetic location. You then need DataAirPopulator.exe which is on the website You then need to click on ModeSlog.mdb and popthree.mdb in the c:/GFIA/populator directory & run each of these once Start SBS either from within the database or by running PacModeS Populator 3.0 BETA 4.exe which should be in the BaseStation directory. Check it is working as expected (Then start on the PlanePlotter install if you want it) Problems (1) I wonder if anyone can help. I have just tried to set up a new net book for my USA trip next week. I have ‘basestation’ working and Database working but when I try to run the DataAir Populator I get ‘Can’t find data’ error with ‘pop3.mdb’. It then says that ‘c:/ populator/ modeslog.mdb’ is an invalid path. I have checked that set up on my laptop that works and replicated the DataAir file, kinetics file and ’gfia’ folder. If I put the Populator file into just ‘c:/’ I get ‘modeslog.mdb’ to run and also ‘pop3.mbd’ to open and build tables. If I then go back into ‘gfia’ folder and run it there I get the tables to build. However when you open ‘basestation’ via the beta ‘pop.exe’, the registrations, aircraft type etc don't show. I have tried uninstalling ‘gfia’ folder and downloading again several times but to no avail. Any help would be appreciated. (Ronnie Carpenter) In the "gfia" folder there is a sub folder called "populator". Inside this you have to double click the modeSlog.mdb, wait for it to shut down, the n do the same with the popthree.mdb file. You might get an error on this one, just click OK and carry on. This should link the Populator to the database. After that, inside you database you have to do a "Build HEX data" (something like that). It should then work as long as you also ran in your member key. (Stu Telford) (2) Windows 7 Leon notes that Windows 7 can be a bit picky. Kevin Evans notes that if you are using Windows 7, you will find that if you follow the above steps, the file popthree.mdb will spring up an error. No solution found as yet. 5 [email protected] v2 16-9-13 Pacific Database Wiki Getting Restarted Downloading a totally new Database Instead of having to download a bare database and then load each individual update in order, a new partially pre-loaded database can now be downloaded. email Bob Clarke at [email protected] and ask for the download link to the new database install it ONCE YOU HAVE INSTALLED IT and checked that it's working, email Jim Bavin at [email protected] and he will send you an unlock key so that you can download any remaining updates 6 [email protected] v2 16-9-13 Pacific Database Wiki Starting the Database - don't double-click the icon When starting the Database, don't double-click the icon. If you do, it will open two copies of the database and then, when you click on 'Load and Open', it says 'Opening' but never completes. You then have to click 'Close and Leave' to close one copy of the database then click 'Load and Open' to open the remaining copy of the database. 7 [email protected] v2 16-9-13 Pacific Database Wiki Screen Resolutions Trying to use a screen resolution that isn't supported will stop the database opening. A few users have found this when nothing happens after they press the 'Load and Open'. Barry Stuart advised the following supported resolutions: Supported The following screen resolutions are supported: o o o o o o o o o 1024x768 1152x864 1280x720 1280x768 1280x800 1280x1024 1440x900 1680x1050 1920x1200 Not Supported The following resolutions are NOT supported: o o o 800x600 1024x600 1280x600 If your screen resolution isn’t a supported one, then reset your screen resolution in Control Panel to one of the above. Note that your PC will then remain at this screen resolution for any other work that you do. Res-o-Matic There is a program that enables screen resolutions to be set for specific applications then they revert to the ‘normal’ resolution for other work. The program is Res-o-Matic and is reviewed at http://www.inspectmygadget.com/2008/02/25/windows-software-change-the-resolution-of-a-singleprogram-with-res-o-matic/ and is available at http://www.bcheck.net/apps/reso.htm BUT when this is downloaded a virus warning is flashed up on the screen. Whether there is a virus in the program is not known - no one has yet continued with it. Do so at your own risk. 8 [email protected] v2 16-9-13 Pacific Database Wiki Date Formats Date formats should be Short Long dd-MM-yy dd MMMM yyyy A Member noted “I have an old version of Office 2003 with formats: Short Long dd/MM/yyyy dd MMMM yyyy The options I have for short date are dd/MM/yyyy dd/MM/yy d/M/yy d.M.yy yyyy-MM-dd If I change the separator from ‘/’ to ‘-‘ then the date changes to ‘yyyy-MM-dd’ and the database does not open.” To set the correct format Go into Control Panel and under ‘Region and Language - Formats’ Change the date to the required formats. Alternatively, in ‘Region and Language - Formats - Additional settings’ Date tab, under ‘Date Formats’ type what you want. Leaving the ‘/’ indicates a directory which isn’t there. Pictures from Peter Watson 9 [email protected] v2 16-9-13 Pacific Database Wiki Printouts Some functions of the database cannot be printed out directly. What you have to do is use the Windows key combinations as illustrated below. Museums Q: I want to output a list of the aircraft in the museum at Brussels. I've called up the details of the museum and then clicked on the 'green book' icon and get the options of xls, or rtf (plus others). I have tried both of these options and then go into 'DataAir' and click on 'Reports'. There is a 'weird' coloured icon listed 'Brussels' with a text file called Set in both the RTF and Excel folders. In both cases the 'weird' icon registers 0 bytes. Is this one of the functions that no longer works? If so does anyone know a way to get the listing I want? A: (Thanks to Peter Watson) This works: Bring up the museum list Place cursor in left black column at the top, click "ctrl" + "A" (this selects all the data) click "ctrl" +"C" (this copies it to the clipboard) Open a blank excel sheet and put cursor in top left box and press "ctrl" + "V" (this inserts the data) You may have to change the font colour afterwards Note: this procedure may work with other instances where the printout facility does not work properly. 10 [email protected] v2 16-9-13 Pacific Database Wiki Your Own Data Where is it? Great care was taken by Barry Stuart when he programmed the database to ensure that your own personal logging data was kept separate from the database files. You will find your data in the directory that you created for your backup data. In your directory, look for a filename which looks like xx_PRIVATELOGS.MDB where xx is the highest number of the files of this form, corresponding to the latest backup data. To see your data, you need to double-click this file to open it in Access. You will see that your data is split between six tables. These are linked as necessary via the 'ID' value (of an individual aircraft). These contain: Flog logLLp logLLs MyProfile PerNote tblPhoto details of your Flight Log - the aircraft that you have flown in the aircraft that you have logged, with date and location the aircraft's operating unit and codes profiles that you have created your personal notes against your logged aircraft your photo log Your data is therefore kept securely outside of the database software. Should you ever choose to use another database, or to manipulate your loggings outside the database, your data can be readily retrieved. How can I retrieve it? In order to retrieve your personal loggings data, carry out the relevant procedure given below. This places all your data into a single Access datasheet and includes the option of exporting it into an Excel spreadsheet where you can manipulate it as you want. Access 2003 and Access 2010 have slightly different steps. Access 2003 Find your loggings Go to the folder where you have saved your backups Copy and paste your latest backup file: it's called "xx_PRIVATELOGS.MDB" where xx is the highest number of the files of this form, corresponding to the latest backup data IMPORTANT: Work from the copy to keep your original safe Create and run a new Query Open (double-click) "Copy of xx_PRIVATELOGS.MDB" Opens with a table showing 'Outstanding Loggings' 'Close Form' select 'Create' tab select 'Query Design' in 'Show Table' dialogue box, 'Tables' tab select 'logLLp' 'Add' similarly, select 'logLLs' 'Add' 11 [email protected] v2 16-9-13 Pacific Database Wiki 'Close' in the 'logLLp' box, double-click '*' in the 'logLLs' box, double-click '*' From the toolbar, click on the ruler/pencil/set square icon on the left (it's under the File menu on mine but is a moveable toolbar so could be anywhere!) and select 'DataSheet View' All your records will now be shown. Four columns - 'flag', 'LOCKK', 'logLLs.ID', 'logLLs.when' - may not be of much use, but keep them. They can be hidden or deleted later. You can now export your data to several different programs e.g. Excel, PDF Access 2010 It is expected that the keystrokes for Access 2007 are identical. There are 2 methods given of retrieving all of your data: 1. 2. The first extracts all your data by inputting SQL code into an Access query and running it. PREFERRED WAY - Our thanks to Al Henderson for providing the SQL code to enable this to be done The second extracts your logging data but not your personal notes fields data by specifying an Access query and running it. STEP 1 - Find your loggings Go to the folder where you have saved your backups Copy and paste your latest backup file: it's called "xx_PRIVATELOGS.MDB" where xx is the highest number of the files of this form, corresponding to the latest backup data IMPORTANT: Work from the copy to keep your original safe STEP 2 - Create and run a new Query METHOD 1 Open (double-click) "Copy of xx_PRIVATELOGS.MDB" Opens with a table showing 'Outstanding Loggings' 'Close Form' select 'Create' tab select 'Query Design' close 'Show Table' dialogue box in 'Design' tab, select 'Data definition' in the blank pane type SELECT logLLp.when, logLLp.Where, logLLp.Registration, logLLp.Aircraft, logLLp.Operator, logLLs.logunit, logLLs.[loga/c code], logLLs.notes, pernote.mynote FROM (logLLp LEFT JOIN logLLs ON (logLLp.when = logLLs.when) AND (logLLp.ID = logLLs.ID)) left join pernote on logllp.id=pernote.id 12 [email protected] v2 16-9-13 Pacific Database Wiki WHERE (((logLLp.when) Is Not Null)) ORDER BY logLLp.when, logLLp.Where, logLLp.Registration; 'Run' All your records and the personal notes field data will now be shown Optional If you want a different order of variables and records, either o Rearrange the SELECT variables to give the order of the columns that you want & Rearrange the ORDER BY variables to give the order in which records are sorted, and run it, or o Manipulate the resulting datasheet using the Access facilities, or o Export to Excel and manipulate the data there (see STEP 3) If you want to save the new Query (to rerun, copy the coding into a later backup [as opposed to copying it from here] ) ; o 'File' o 'Save' o enter a name for the Query in the 'Save As' box o 'OK' METHOD 2 Open (double-click) "Copy of xx_PRIVATELOGS.MDB" Opens with a table showing 'Outstanding Loggings' 'Close Form' select 'Create' tab select 'Query Design' in 'Show Table' dialogue box, 'Tables' tab select 'logLLp' 'Add' similarly, select 'logLLs' 'Add' 'Close' in the 'logLLp' box, double-click '*' in the 'logLLs' box, double-click '*' 'Run' All your records will now be shown Four columns - 'flag', 'LOCKK', 'logLLs.ID', 'logLLs.when' - may not be of much use, but keep them. They can be hidden or deleted later. You can now export your data to several different programs e.g. Excel, PDF STEP 3 - Export to Excel - the most flexible program option select the 'External Data' tab in the 'Export' part of the ribbon (menu bar), click 'Excel' specify the destination filename and format o File name o File format specify export options - there are 3 options (for now, just do the first two options) 1. check/tick the box: Export data with formatting and layout 2. check/tick the box: Open the destination file after the export operation is complete or - if you have selected certain records before the export 13 [email protected] v2 16-9-13 Pacific Database Wiki 3. check/tick: Export only the selected records 'OK' Your loggings now open in Excel for you to manipulate as you wish. 14 [email protected] v2 16-9-13 Pacific Database Wiki Finding an Aircraft Type - Checking if the type is already in the database It is often not obvious how a type is named in the database - for example: When the original designer/manufacturer is a historic one, not a current one For many smaller, less well-known, aircraft types, references to the type may not mention them Where the punctuation is unexpected e.g. I.C.P. - not ICP The routine below provides an easy way to check if a potentially new aircraft type is already in the database. • • • • • • • • Select ‘Data Admin’ Select ‘Show Data Stats’ Click anywhere in the blank 6th column ‘ctrl’ + ‘A’ (selects all data) ‘ctrl’ + ‘C’ (copies all the data to the clipboard) Open a new blank Excel spreadsheet Click in the first cell (A1) ‘ctrl’ + ‘V’ (inserts the data from the clipboard) (You may have to change the text colour in Excel to something other than white to be able to see anything) • Select Excel’s search icon (binoculars) • ‘Find…’ • In ‘Find what:’, Insert part of the type’s name that you are interested in e.g. MXP (or mxp) [choose an obvious part of the name to yield a range of results to choose from] • Select ‘Find All’ • Results are listed at the bottom of the dialogue box • Check the results to see how the type is named in the database • If not listed, then request a new type on the Pacforum website At 15-10-11, 3755 aircraft types were listed 15 [email protected] v2 16-9-13 Pacific Database Wiki Requesting New Types and/or Locations to be added You can request new types and/or locations (e.g. airfields, museums) to be added by going to the Pacific Database website at http://www.gfiapac.org For a new type, first check if the type has already been requested: select 'Members Only Section', 'Data Requests', 'Types', 'Current Request List - PacEditors' If it has not, then select 'Members Only Section', 'Data Requests', 'Types', 'New Types - Add Request' and fill out the request form. For a new location (e.g. airfield, museum), first check the main database; o for Airfields: 'Search', 'Airfield:-Name', select country from dropdown menu, click on the next dropdown menu to get a listing of airfields currently in the database. Sometimes the airfield may be known under a slightly different name and already be in the database. If it is not already in, email your request to Bob Clarke giving as much detail as possible e.g. full name of airfield, ICAO code, IATA code. o for Museums: 'Museums / Bits', 'Museums', select country from dropdown menu, click on the next dropdown menu to get a listing of museums currently in the database. Sometimes the museum may be known under a slightly different name and already be in the database. If it is not already in, email your request to Bob Clarke giving as much detail as possible e.g. full name of museum, town/city, country. 16 [email protected] v2 16-9-13 Pacific Database Wiki Downloading Updates Updates issued to date can be downloaded from the Group's website at http://www.gfiapac.org from the 'Members Only Section', 'Update Files - PAC2011'. New updates are emailed to members by Bob Clarke via the [email protected] newsgroup. 17 [email protected] v2 16-9-13 Pacific Database Wiki Updaters' Areas of Responsibility The list of Updaters' areas of responsibility is given on the Group's website at http://www.gfiapac.org in the 'Members Only Section', 'PAC Editor Coverage'. 18 [email protected] v2 16-9-13 Pacific Database Wiki Information for Updaters Topics covered are How to update records New record - Making changes to an Update before it is Released to Everyone - IMPORTANT Updating to 'Preserved' Deleting an Operator Reducing the number of Duplicates How to Update Records A write-up by Kevin Jacomb based on the advice given to him by Jim Bavin, is given below. Any amendments and additions are welcomed Needs rechecking by Jim Sending in Updates Main Menu page “Data Admin” “Update Review” Click “Produce Update” box Right-click “nKJoutupdate.mdb” in the “c:\DataAir” directory where n = number of update automatically produced Send to “Compressed (zipped) Folder” Email resulting “nKJoutupdate.zip” file to Bob Clarke o Email to "[email protected]" o Message header = “[Update] n” where n = update number o Attach file "nKJoutupdate.zip” Frequency of Update Submission Jim sends one in when he has updated 50-100 airframes For me, may be 1-2 per month Say, after LAAS and ABN done for one month, or a whole register done Avoid submitting very small quantities. They are checked! New Operator Main Menu page “Data Admin” “New Operator” Enter New Operator name into “Check existing operator names” Enter Click first dropdown “(blank) X” Enter Type New Operator Enter Select Country code from dropdown If known, type in 2 letter code, else leave as “-“ (note – do NOT delete “-“ as db does not accept a null) If known, type in 3 letter code, else leave as “-“ (note as above) 19 [email protected] v2 16-9-13 Pacific Database Wiki If known, select Type of operator in dropdown. Else select "Business Operators" (note as above) Click “Save” button appearing Click “Exit” New Record Main Menu page “Data Admin” “New Record” Minimum data to enter is o Manufacturer o Model Series can be left as “-“ Variant can be left as “-“ o Current Registration Date If not known enter as “00-00-00” o Registration At least the country e.g. CNo Civil / Military o Operator If not known enter as “Unknown” from dropdown o Status o Click “Add” button appearing o Click “Add Previous” button appearing if want to add previous registrations IMPORTANT NOTE: Once you have saved the completed New Record, you MUST NOT add any further updates to that record until it has been sent to Bob and subsequently has been sent out to everyone as a formal database Update. Any such further edits will show on your own copy of the database but will NOT be added to the Master Database and everyone else's copy. For further details, view the correspondence on this here. Note for “Cameron Z-425LW” “Cameron” = Manufacturer “Hot Air Balloon” = Model from dropdown “-Z-425” = Variant from dropdown “LW” is omitted (would have to be requested as an addition) New Base If not in base dropdown, email Bob Clarke off-Forum Re-Registration Click “Re-Registration” box Add “day number” in dropdown box to left – if don’t know, select “00” Add “month number” in dropdown box appearing to the right – if don’t know, select “00” Add “year number” in dropdown box appearing to the right – if don’t know, select “00” Add “Serial” Skip "Occurence No." small box unless this is a repeat registration e.g. if reused once = 2. NB: same as "acur" Select “Country Code” in dropdown appearing to the right Select “Operator” in dropdown appearing to the right Select “Civil or Military” in dropdown appearing to the right 20 [email protected] v2 16-9-13 Pacific Database Wiki Select “Status” in dropdown appearing to the right Select “Update” box or “Abandon” box Operator Change Check first that new operator exists in the db Click "Op. Change" box Add “day number” in dropdown box to left – if don’t know, select “00” Add “month number” in dropdown box appearing to the right – if don’t know, select “00” Add “year number” in dropdown box appearing to the right – if don’t know, select “00” Select New Operator in dropdown appearing to the right Select “Update” box or “Abandon” box Written Off (W/O) Select “Written Off” box Add “day number” in dropdown box to left – if don’t know, select “00” Add “month number” in dropdown box appearing to the right – if don’t know, select “00” Add “year number” in dropdown box appearing to the right – if don’t know, select “00” Type in details into Text Box appearing to the right. Keep concise Select “Save” ? box Routine automatically moves current registration down to Previous box, replaces it by “Canx” Civil / Military Applies to the service e.g. 7T- for Algerian Air Force = Military. Is this still the case? CIA aircraft are more problematic (probably = civil) If Cancelled by Authorities Select “Dbr” box “Status” will show “Dbr” – change in dropdown to “Status Unsure” “Final Fate” shows “Dbr” – change in dropdown to “Cancelled by Authorities” Group Notes For anything you want everyone to read Keep short For example, Jim uses them for recording o Manufacturers c/n (the CAA uses the PFA/LAA number for the register) o CofA expired, date Cancelling an Editing Mistake Can’t cancel in Edit page Come right out of the aircraft record to main menu Go back into aircraft record and correct by new edit Can submit multiple edits for the same aircraft in the same Update submission NEW RECORDS - Making changes to an Update before it is Released to Everyone - IMPORTANT Once you have saved the completed New Record, you MUST NOT add any further updates to that record until it has been sent to Bob and subsequently has been sent out to everyone as a formal database Update. Any 21 [email protected] v2 16-9-13 Pacific Database Wiki such further edits will show on your own copy of the database but will not be added to the Master Database and everyone else's copy. When you add a new airframe, a flag is set to 'N' for 'New'. If you then amend it (say to add a HEX) before sending the update, this will reset the flag to 'U' for 'Update'. However, because there is now no 'New' record to apply the Update to, it fails. Wait until your update is released in a formal Update to everyone, then make any further updates. For further details, view the correspondence on this here. Updating to 'Preserved' Q: I have an aircraft which has been cancelled by the authorities. It's still preserved in a museum. I have updated the status to 'Preserved - non flying' and added the preservation details. The registration still shows as current. Should I also do a 'Dbr' on the record to cancel it? A: If by 'Dbr' you mean the macro on the edit screens then I would say no as this will cancel the registration and the frame will not show up in the museum listing. The best way is to complete the 'Final Fate:' section of the record manually and that way the registration is left alone and so is the museum listing. Deleting an Operator This has to be done centrally. email your request to Bob Clarke. Reducing the number of Duplicates All editors should have a look at the duplicates in an effort to reduce the number. To do this, Steve Leach advised (29-1-13): If you go into 'Data Admin' and click on 'Duplicates you will bring up a list currently standing (Jan 2013) at 3158 of records which should have a number of records with the same registrations. Some will be just the country id such as G or N but others will be of a full reg but of two different types or the same type that have different c/n or have been put in by a updater who hasn’t checked if it is already in the database.It will also contain a list of military serials which are genuine duplicate serials but issued by different countries. If there any duplicates in your area of updating then you can investigate and amend the records if possible. 22 [email protected] v2 16-9-13 Pacific Database Wiki Updater Key Just done some updates but when I try and produce the update after pressing the produce update button the little blue circle appears for a couple of seconds then nothing else happens. Can anyone help with a solution? … I think that this may be the first updates I have done since I updated to windows 8. (Gordon Smith [GS]) Close the d/b and look in the DataAir folder and see if there are any .ldb files in there (Kevin Evans[KE]) Did you simply upgrade or was it a new installation? (KE)……. Just upgraded. Everything else on the database works though (GS) I can see the details of the updates I have done just won’t produce the update. You don’t think it may have lost its updater status do you during the window upgrade? (GS) Does the update just show in the screen where you can leave and exit or produce update? (KE)…. Yes, I use the update review option from the data admin menu, then at that screen with the produce update and leave/exit buttons at the bottom, the details of the updates I have done show under the relevant tabs as usual. It is then when I click on the produce update button that the problem occurs. (GS) You may be right that the updater status has gone adrift within the registry. I’m not sure if there is anywhere in the database which can tell you if you have updater status or not. I would have a word with Jim Bavin and see if he can give you a new updater key.(KE) You will also need to ask Bob for the number of the last new record you put in, in update 82. Then I can produce a key for you. I think you will have to re-do your current update though....If we get these record numbers wrong (duplicated....mayhem reigns. He will normally send me the info if you ask him (Jim Bavin) The suggestion that the registry is goosed is quite correct. Whilst Microsoft have done a god job with the update/migrate routine, it can only go so far. I will send the relevant details to Jim later this evening so that he can create the new key. (Bob Clarke) 23 [email protected] v2 16-9-13 Pacific Database Wiki Regular Maintenance There isn't much that you need to do on a regular basis - just a few things: Watch the Forum messages on the Group's Google Groups site at http://groups.google.com/group/pacificforum?hl=en for new updates to download Compact your database monthly - do this by selecting from the database's main menu: 'Data Admin' > 'Compact'> double-click 'Continue >>>>>>>>'. Failure to do this will result in a massive database and potential problems. Jim Bavin does his best to send out a monthly reminder for us all to compact Make a backup copy of the following file: c:\DataAir\RunDataAir.mdb Occasionally this can become corrupted and cause the database not to open. Replacing it with a recent backup will do the trick Frequently backup your loggings from the home database screen via: 'Personal Data' > 'Backup' 24 [email protected] v2 16-9-13 Pacific Database Wiki Working with Access 2007 & 2010 Compared with Access 2003, the 2007 & 2010 versions need a few tweaks. These centre on the need to make the database files 'trusted'. Comprehensive input just deleted - SHRIEK! Being rewritten 25 [email protected] v2 16-9-13 Pacific Database Wiki Working with Windows 7 The database works with Windows 7 but some tweaks are required. Experiences by members are noted below. The following emails reported how members got the database to work with Windows 7 Paul Bailey reported on Monday, July 18, 2011 12:32 AM Subject: Re: RE NEWLAPTOP FINALLY OR NEARLY I have just installed basestation and populator on my Windows 7 home premium laptop. When basestation was loading I changed the path to C/Programfiles and it installed there OK. After that I loaded the populator to C/PROGRAMFILES/KINETIC/BASESTATION and it worked OK! Leon Loberman reported on 25-06-11 22:15 If BaseStation and PacModeS are not in the C:\Program Files\Kinetic\Basestation folder then I’m afraid it isn’t going to work. From what you’ve said, it looks like you’ve got the 64Bit version of Windows 7 and therein lies your problem if you want to run PacModeS. Windows 7 64 bit will force the programs into the x86 version of the folder and PacModeS just can’t handle that….. Leon Loberman reported on 18-07-11 22:15 For the record, here's what we did: 1. Despite all efforts, Basestation would not install anywhere except in the Program Files (x86) folder - the last install was run with the Setup program configured to run in Windows XP Service Pack 3 compatibility mode and run as administrator. This was using version 1.1.159 of Basestation 2. Having installed there, we then manually copied the entire Kinetic folder to the Program Files folder and successfully started Basestation - this was then receiving message from the USB connected SBS. 3. We then ran the DataAirPopulator.zip installer program, which created a c:\GFIA folder - however it did not create the populator sub folder - instead it put the ModeSlog and popthree files in the GFIA folder. 4. We then tried running ModeSlog which had a message saying it could not apply the command but closed ok and popthree which said it could not find the ModeSlog file - this is because it was looking for the populator 26 [email protected] v2 16-9-13 Pacific Database Wiki sub-directory. So I created this sub directory and copied all the files from GFIA into this sub-directory, reran ModeSlog which still gave the same message and reran popthree which didn't give any message and just closed as normal. 5. We then ran PacModeS Populator 3.0 Beta 4.exe and lo and behold everything started ok….Harry is back in the world of RQ's, Ps's and Unk's . 27 [email protected] v2 16-9-13 Pacific Database Wiki Working with Office 2013 The only problem at all that I have encountered since changing over to Office 2013 is that I always get an error saying "Cannot find object Autolog" during opening, even though the Autolog routine is there, and more importantly works as normal. If anyone else is brave enough to switch over to the new Office, or already has done, please let me know if you have this error. Also, if there are any programmers or Access experts out there, is there a way to set a macro to ignore errors like this ? (Stu Telford) -----Answer awaited----- 28 [email protected] v2 16-9-13 Pacific Database Wiki PacReporter I recently had a problem develop with my PacReporter. Things were slowing down. To rectify my problem, I simply replaced all three files i.e. modeslog, pacreporter and popthree with copies from my lesser used laptop. Not only did this cure my error but also improved speed. I didn't even need to double click each file as you do when you first install. The only thing I did after the switch as a precaution was to rerun the hex build before use. (Kev Hart) -------------------------------------------------------------------------------- I have noticed over time that when Pacreporter runs after I close down Basestation it is taking an absolute age to finish. Sometimes around 20 minutes or more. I really don't need to see the really old logs from years ago. Is there any way I can delete this data so that it (hopefully) runs a little quicker ? If anyone knows where these logs are stored I could take a look around in MDBPlus. (Stu Telford) -----Answer awaited ------ 29 [email protected] v2 16-9-13 Pacific Database Wiki Integration with Planeplotter The Planeplotter software program receives and decodes live digital position reports from aircraft and plots them on a radar-like display. Planeplotter has three major features plus a lot of add-on facilities provided by its users. Its major features are: Hundreds of users share their SBS-1 signals with everyone. This gives you extensive coverage and counteracts any local obstructions that you may have from, for example, hills. The one-off cost is Euros 25 + VAT. There are a number of aircraft, notably military types and Flybe, which show in the listing on the SBS1 but which do not transmit their position and so do not plot. Provided that there are sufficient suitable users receiving such an aircraft, PlanePlotter can determine the position using the arrival time of the Mode-S transmissions at each user. Multilateration therefore enables them to be plotted. It is free for users who regularly provide raw data into the system on a near 24/7 basis; other users pay Euro 12 + VAT per year. For the later SBS-1e/er sets, a facility called Beamrider and Beamfinder Plus enables PlanePlotter to use the pings from known radar stations to calibrate the radar's rotating beam and to use that information to locate aircraft not transmitting position. Beamfinder Plus can even locate an aircraft without Mode-S transponder. Both PlanePlotter and Multilateration can be downloaded and used free of charge for 21 days before you have to sign up and pay. Full details are available on its website at http://www.coaa.co.uk/planeplotter.htm Leon Loberman has developed a software routine which uses our database to decode aircraft signals and to identify on the screen which aircraft we still 'need'. The latest version (as at 14-6-13) of Leon's routine can be found by going to http://www.gfiapac.org/?page_id=39 and selecting PacModeS2012_v147_Install.exe Leon is working to fully integrate the database with Planeplotter so that the database can be updated from the Planeplotter screen, as our Populator program currently does. 30 [email protected] v2 16-9-13 Pacific Database Wiki Your Problems and Solutions Some of the errors that members are coming across and their suggested solutions are given below. My log stats screen is completely blank Check your date format settings: set your short date to dd-MM-yy and the long date to dd-MM-yyyy ensure that the date separator is set to a '-' (dash), not a '/' (slash). Sometimes it reverts back to the factory setting My database won't open; when double-click the 'Load and Open' button, it says 'Opening' but then does nothing Encountered by Mick 10-9-12, Kevin Jacomb 1-10-12 Suggestions made: ***** THESE ARE THE MOST COMMON SOLUTIONS TO OUR PROBLEMS ***** Not a screen resolution problem, is it? Check with a different resolution in case that fixes it (Al Henderson, Kevin Evans) Navigate to the DataAir Folder and scroll down to dtset.mdb. Right click and you should find “Restore previous versions” Click on that. This method works on my Windows 7 operating system but you might want to make a copy of dtset.mdb and rename the copy first (Peter Watson) The "Restore previous versions" option seems to be a Windows 7-specific option - not available on XP (Kevin Jacomb) Have you got an extra file in your DataAir folder? Do you have both 'dtset.mdb' and 'dtset1.mdb'? You should only have one 'dtset' file. The 'dtset.mdb' file will have been corrupted. You need to rename 'dtset.mdb' to, say, 'dtset2.mdb' as a temporary backup. Then rename 'dtset1.mdb' to 'dtset.mdb' then try to reopen the database. Then delete 'dtset2.mdb'. (Steve Sutcliffe) You haven’t got a locked version of the database in your DataAir folder by any chance, have you? It will be something suffixed .ldb…. (Leon Loberman) If so, delete the .ldb file (Kevin Jacomb Just a thought - have you compacted recently? Wondered if that may be the cause (Gordon Smith) All you need to do is re-instate 'RunDataAir.mdb' from a previous backup taken when you know your database was working and replace it into your 'DataAir' folder. (Kev Hart) Worked a treat for Kevin Jacomb Note that this is what some people refer to as "reloading a new front end" Noticed we were without a Boeing logo so I have added one for your Sysda folder (John Robinson) - but how do we find which number a gif file should be allocated for an airline? I pull a fleet listing and if it does not have a logo I click on the little book by the printer icon at the bottom of 31 [email protected] v2 16-9-13 Pacific Database Wiki the page then the 'txt' icon the routine will fall over at this point and tell you what gif is missing with the number associated to that operator. (John Robinson) When I open the database, it loads two copies (Kevin Jacomb) The second one opened automatically before you could stop it. Editing the database was OK but on exit, the 'Close and Leave' button gave an error message that there was a problem and the database had to be repaired. It asked for a new filename for the 'RunDataAir_Backup.mdb' file. After giving a new name it closed but then the second copy displayed the 'Close and Leave' button. When double-clicked this closed normally. Solutions tried included different ways of opening - via a shortcut, and via the 'RunDataAir.mdb' in the 'DataAir' folder - and Barry offered advice but all solutions failed. It was something to live with but it did cause Bob some problems of duplication when updates were created. By chance, Access 2010 was loaded some months later and the problem never repeated. It was probably some form of corrupted Access 2003 file(s). 32 [email protected] v2 16-9-13 Pacific Database Wiki Limitations and Issues There are a number of limitations known for the database. Some of these are due to Updaters' time delays; some by inherent software limitations. These are as follows: Updater Limitations Delays for new types to be added - you can minimise this by providing the maximum amount of supporting data when you request a new type to be added Delays for new locations (e.g. airfields, museums) to be added Software Limitations EXIF photo facility The EXIF facility works fine with aircraft photos added directly from a camera's memory card. However, where photos have been produced by scanning in hard copy images, the photo information recorded and the operator data taken from the database will reflect the date at which the image was scanned, not the date that the original image was taken. To get around this, 'work arounds' have to be adopted: o 3rd party software has to be employed to change the dates as a batch o check The Operators have to be reset by using the correct operator codes. These are currently (September 2011) being compiled. Printing Software Issues Copyright Barry Stuart holds the copyright on the software, and no further changes to it are anticipated by Barry, nor can anyone else change it under law. It is therefore in its final form. Fortunately there is nothing fundamental missing from it. The software limitations given above are irritating but not 'showstoppers' to its successful use. Note that the copyright for the data within the database is owned by us, the members. Future Operating Systems The progression of Windows operating systems from XP to Vista to Windows 7 has necessitated minor tweaks when setting up the database to ensure that the database will work correctly. However, whether future updates of Windows can accommodate the database, no one can know. This is a potential risk for every bit of software. o Windows 8 - at the Sept 2012 AGM, Jim Bavin reported that Windows 8 is aimed at touchscreen systems. In essence, the cursor is used like a finger to swipe the screen/page, as with tablets and smartphones. It also lacks obvious information - you can face a blank screen and have to know how to uncover hidden menus to progress. Fortunately Kevin Evans has managed to get the database working on Windows 8 but at that time had not got Mode S working. Future MS Access Versions The database was designed to use Microsoft Access 2003. Minor tweaks in setting up Access 2007 and Access 2010 have been required. How long future versions of Access can accommodate our database and others' databases is an open question. o MS Access 2013 - at the Sept 2012 AGM, Bob Clarke strongly recommended that we do not buy Access 2013 as it is very likely to require major reprogramming of the database to handle it. Such a task cannot be supported. 33 [email protected] v2 16-9-13 Pacific Database Wiki If the database were not able to use future operating systems or Access versions, the only options would be to continue with the older systems and software as long as possible and to explore the cost-effectiveness of creating a wholly new database with which to manipulate our data. Note, however, that all aircraft databases would suffer the same problems. 34 [email protected] v2 16-9-13 Pacific Database Wiki Supporting Pages The following pages contain information which is hyperlinked into the main sections of the WIKI. Mdb & ldbs Produce update won’t work - ldbs? 35 [email protected] v2 16-9-13 Pacific Database Wiki Updating Flag Barry Stuart's Advice Bob, et all updaters. This is a very complex issue to answer quickly and easily. In its basic form as you outline below, "Yes", you are correct in your answer, you cant set a flag for updating (U) if the record flag is already set to new record (N)! Reading all of the thread on this mail it becomes obvious that, because of the way the Db is structured, the problem is more complex to understand, and, thus work-around! When I first explained years ago about how the updating process worked it seemed pretty logical to understand, given that the structure was being upgraded and explained to the group as these changes took place. Now I am outside looking in at the updating process and I have to say it looks a bit confusing to try and offer a quick "rules to observe" at the present stage of the Db structure! There are a few things I would suggest need change to try and add some extra protection to an updaters input, mostly around NEW records, because this is without doubt the problem area. I am away chasing railways again next week around Europe, but, as the nights will be longer I will take a pen and paper and try to cobble together a potential solution to the problem. First thought is to make a new record NON-UPDATABLE by the updater who added it till such times as the record has been produced through the master Db and thus out to the group. Initial thought, not easy to initiate a logical (Db wise) argument. One option, but avoiding the Db argument path. When an updater holds NEW records he is forced to produce these in an update out to the master Db before he can close the Db session he added them in. Argument for this method would be to protect new records in case the PC went down before update was produced (reasonably easy to do by setting N flag to M? flag only after update is ready for sending to master) and then is held at (say) M? on the updaters Db till the update from the master to the group is run back in to the updaters Db, at which point M becomes the default archive flag of A! If this option is followed through then you will only add one new letter to the updating production scripts (M in this instance) and you would only be dealing with a minimum amount of recode work. Note, it will be minimal, but it WONT be a walk in the park job, it will need thinking through and it will need testing out at each stage! To pre-empt the question "Why" can this problem happen? The Db was, years ago, built as a flat field structure, as a lot of Db's still are! It has evolved over the years into a fully relational system and this opens up potential problem areas when a Db is being used in a non closed environment (updated by many users who are not all working on a single Db (master copy) outside a network) In a nutshell. When a new record is entered there is initially only 1 record table, the core data. If a previous reg is added at the same time it then adds a new record to the history table, an airfield, new record to the fields table, and so on and so forth. But it ONLY adds these new records to tables if you add all this data at the same time. Move to another record and your new record is available to you, the creator of that record, till such times as its been through the system! Barry ………………………… From: Bob Clarke [mailto:[email protected]] Sent: 15-10-2011 19:53 36 [email protected] v2 16-9-13 Pacific Database Wiki To: '[email protected]' Subject: RE: [paceditors] Attn Bob re AB47 Doug, et All. This issue was discussed on the group quite some time ago. Stu Telford raised the initial concern following instances of updates not being reflected in the database even though Stu had put the updates in. My understanding, and I do not mind being corrected, is that once you have updated a record, a flag is set to denote a change has been made. Subsequent changes will not influence this flag until it has been run through in an update. Now the problem, you enter a new frame into your copy of the Db, this will flag the frame as (N)ew and will find its way into the database once run through the master. At the point you entered this change, the database routine did a sweep of what had been added and identified these records for the update. This implies that once the update check routine has run, it does not re-run following additional material/information being added. This has been checked and verified with Stu. Now, if this is not the case, then why have we so much concern about missing “bits” that are known to have been added but are not evident through the master database. I have copied Barry on the email to see if he is able to confirm or refute observations. For the future, I would recommend that once you have added or amended a record and saved it to an update, leave it alone until it comes through the master. If I get any more info on this I will post it to the group. Bob From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Tillie Sent: 15-10-2011 19:03 To: [email protected] Subject: Re: [paceditors] Attn Bob re AB47 That might be our best bet, Al........maybe Bob will be able to shed more light on this for us. Doug. ----- Original Message ----From: Al Henderson To: [email protected] Sent: Saturday, October 15, 2011 2:24 PM Subject: Re: [paceditors] Attn Bob re AB47 Doug, I may well be in the same position, although having only been doing it a few months, the potential for problems is a lot smaller. Like you I don't keep a list of updates I make so can't really check. Might be we just have to move on and fix any problems as and when they arise. Cheers, Al. 37 [email protected] v2 16-9-13 Pacific Database Wiki On 15 October 2011 13:51, Douglas Tillie <[email protected]> wrote: Appreciate your response, Peter. Given that you were not aware of this problem either I'm now even more concerned........the thought of deleting and inputting again is scary to say the least (I don't keep a separate note of each frame I update).....not just in terms of the numbers of frames involved; more with identifying the records that are suspect. My question, to Bob, is can he glean the data from my / your copy of each database to fill any gaps......? One other question would be why when an update is produced does it not simply compare the after with before and present the differences.......that's certainly what I was led to believe at the outset. I think it's now essential that we have a standard procedure for all of this......how many other updaters are in the same position as ourselves....? Kind regards, Doug. ----- Original Message ----From: peter watson To: [email protected] Sent: Saturday, October 15, 2011 1:35 PM Subject: RE: [paceditors] Attn Bob re AB47 Hi Doug Thank you for your note. I, for one, was not aware of this problem and am probably in the same situation as you. In many instances I have updated items prior to submission. In some cases you have to take 2 attempts as not all fields can be accessed on the New record screen. If these are not picked up then a lot of my entries are not complete As they look ok on the updaters machine I don’t know the answer to these historic items. The only thing I can think of is where we know which records are a problem we need to delete and start again. I think where others have tried to do a subsequent amendment that has not worked Regards Peter From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Tillie Sent: 15 October 2011 11:57 To: [email protected] Subject: Re: [paceditors] Attn Bob re AB47 Morning Peter and Bob, That would have been me that added these AB47s......all former French mil examples. All the data I added is showing in my Db however I've been reading the thread about editing new entries before they are issued to the membership that appeared while I was away........is this what is causing the problem do you reckon......? If it is then it is highly unfortunate as I have in the past regularly added new frames then once in the Db add more p.i.s, canx etc. 38 [email protected] v2 16-9-13 Pacific Database Wiki I had no idea that this was an issue however if this does turn out to be the case then I'll ensure that a frame is added purely with one reg and then issued in an update before any other info is added........were all other editors aware of this issue.....as this is surely a significant problem.......does this mean a two level exercise to ensure that all the data is able to be seen for that a/c.......? Given that my copy of the Db has all the data for each of the frames you mention, Peter, does that mean they only exist on my copy and if so how do I get the data to show for everybody. Another question, how do we deal with the many other new frames that I've added and then edited with p.i.s etc.......a very good / or bad example of mine would be the Oz register where since taking responsibility earlier this year I've added several hundred new frames.....and in many cases then added other info before issuing the update.......it seemed correct to get all the info for a frame in place at the one time. In my updates to you, Bob, does any of the data exist that I added.....and if not how do you want to play it......? Look forward to hearing from you. Kind regards, Doug. 39 [email protected] v2 16-9-13