Database Update Requests

[Runway 31]

Jason,

AAL1581 KDFW-KBDL
SWG624 CYYZ-MUVR

Cheers

Alan

[GreekSpy2001]

Alan

C130J AE4E19 11-5731 is down in the db as South Korean Air Force.  However based at Mildenhall with the 352nd SOG

Graham

[Runway 31]

Cheers Graham,  Advised by Paul earlier and my error I'm afraid, havnt a clue what I was doing and its since been corrected but thanks anyway.

Alan

[GreekSpy2001]

ok first chance I had to get to my PC to log in and advise. 

It is set with Autoupdate=Y in my local db when would this update get updated?

Graham

[CYYZGUY]

Hi Alan, another one for you.  Also were you able to update all in post 276?

UAL1622  No Route

regards,

[mikek]

Route not populating:
QFA146 NZAA-YSSY

And a correction:
JST216 WSSS-NZAA-YSSY (each leg is flown by a different aircraft, WSSS-NZAA is an A330, NZAA-YSSY is an A320)

Mike

[mikek]

And another correction:
VOZ76 YBCG-NZAA

[mikek]

And one more correction:
CAL54 NZAA-YBBN-RCTP

Thanks,
Mike

[Runway 31]

Graham,

The autoupdate with the Y is for each individual aircraft and is to show whether to sync with the server or if set to N to leave alone as you have changed something in the record manually and want to keep it that way.  To update the whole database each day, week or whenever you like you go to database explorer and update from there.  Opening up database explorer now shows 2 tabs one of which is database updates and you have two options their either update everything or leave manually changed records alone.  Once you have made your choice and pressed the Start Update button you will see a green line going across the bottom of the window to show the progress and once finished you will be advised to restart RB to finish the process.

In between these updates if you pick up an individual aircraft, if the autoupdate has been set to Y and any changes have been made to the data held in the server, that change will be applied, if set to N, any change on the server will be ignored.
Hope that helps

Alan

[mikek]

And one more not populating
QFA156 NZAA-YMML

Thanks again

[Runway 31]

Thanks for those Mike, appreciated

Alan

[Runway 31]

Jason

UAL1622 KORD-KEWR

I checked post 276 way back on page 15 and the 2 aircraft mentioned are in the database

Alan

[Runway 31]

Its that time of year again where we have changed from the summer to the winter schedules and athe routes database goes haywire.

All RYR, BEE,BAW, and TUI routes have been changed and BER and NLY will be changed for their change over on 1st November.  Also changed are DLH routes in and out of LOWW.

None of the other changes are know to me to they will get amended as and when the details become known to me but already I can see changes to EZY, DLH, QTR and DAL among others so these changes will take time to become known and be corrected.

Alan

[John Racars]

Also changed are DLH routes in and out of LOWW.

Hi Alan,

as far as I can see in my region most of ALL (so not LOWW only) DLH flightid's are changed. Further more until this moment:

AFR
EZS
EZY
GWI

Until sofar I did not see many spectacular changes on the BAW routes...

Kind regards, John

[shouriken]

Here are the results after experimenting with the suggestion of Alan in Reply #1551:
- I've checked "Callsign and Squawk validation" friday evening and saturday morning I've found that most of the unknowns reported in reply 1529 have been populated.
- deleted the record of 4A0689 in the database and the photos and unchecked "Callsign and Squawk validation". Few hours later other wellknown aircraft did not populate (4A5123 YR-TIC and 4A0689 YR-ATI).
- re-checked "Callsign and Squawk validation" this morning, and 4A5123 YR-TIC appeared in the database as soon as it took off (I've missed 4A0689 on its return to LROP this morning).

I've checked/unchecked and checked again "Callsign and Squawk validation" to be sure I can reproduce the problem.