Please don't confuse two entirely different things:
1) The AFCAD having "wrong" airline code. With this, I mean something that can be seen in the AFCAD *ITSELF*, not in relationship with any AI product you are using. As an example, you see a code on a parking that lists an airline that should't be there, or have a parking missing an airline code that you know goes there. Or, a parking with a radius that is clearly wrong.
2) An AFCAD that looks correct, but for some reason doesn't work perfectly well with the AI package YOU use. As an example, a parking has the correct airline code and the correct radius, but that code might not be available in your AI ( it might have changed ), you might miss the model, the AI is wrong, the AI radius is not right.
Problems of the #1 kind are the only ones we CAN and SHOULD fix, and are the only ones we are interested in. Unfortunately, most of the times, when someone comes here saying "Your AFCAD is totally wrong, I remade it myself", when asked to provide a list of ALL the changes, so we can put it back in the AFCAD for everybody to use, the OP usually disappears. Let's hope this is not the case.
Problems of the #2 kind are basically impossible to fix, because if the AFCAD is correct, but not adapted to a certain kind of AI product ( or a *combination* of more than on AI pack ), it's impossible to "fix" it without causing problems to users of different AI products.
Waiting here for reports of the #1 kind, which will be promptly added in the supplied AFCAD, if reported in the correct way. With "correct way", I mean a list that looks like this:
- Parking XX in the AFCAD should have the following codes ( xxx YYY zzz, etc. ) and the radius should be this, for the following reasons....
Again, the reference should be real-world usage. Saying "Parking XX should have this ( wrong ) code, because I'm using AI-product-YY that use an outdated code for the XX company, so I replaced it with ZZ", means it's an #2 kind of issue.
