Is this the way the FMC should handle a missing waypoin...

Hi guysI know you may have more pressing problems, but I thought that this is worth mentioning.On loading a flightplan from EGLL - LFPG the FMC gave the error 'BUREX not in database'. I checked the flightplan, and BUREX is not used, so I ignored it.I selected my DEPARTURE runway and SID for EGLL, then went to pre-select my expected arrival runway at LFPG. I clicked the LFPG ARRIVALS page, and it was totally blank. No Runways, STARs or Transitions.So I loaded the LFPG SID/STAR plate into a text editor (plate attached to this message) and found that 2 STARs use this BUREX ISEC as part of the procedures for this airport (TINIL3E & TINIL3W).So the ISEC BUREX is missing from the current (latest) AIRAC cycle for the PMDG, and BTW is also missing from the AIRAC for FSNav. This is not a big deal really, we have to expect some errors in the AIRAC cycle, it's a lot of work to maintain, and guys like Richard Stefan put a lot of time and resources into it, free of charge.What I am concerned about, is the way the PMDG FMC handled this missing waypoint. It would be quite reasonable to expect that the FMC brings the problem to my attention, which it did, I just didn't know why initially. However, I would also expect it either miss out that unknown waypoint in the 2 STARs effected, or perhaps miss out and ignore the 2 STAR's altogether. I wouldn't expect is the FMC to TOTALLY ignore the WHOLE plate for that airport. Yet that is what it appears to have done.Would it be possible to look at this, when you have time?Great aircraft BTW, I look forward to the 747 release.CheersGraham LaingEDIT: For those of you who may be using or want to use the LFPG plate, here is the missing waypoint. It should be placed in the wpNavFIX.txt file.BUREX BUREX 48.125556 4.440833