10201 Database.zip

[In Libman]

Itwould appear that my current taws terrain data card (010-10201-21) for my Garmin 530W is corrupted or out dated. My Garmin card reader will not detect it. I believe I need a replacement card. Any thoughts or help as to where to find one would be greatly appreciated.

I too am in need of a 010-10201-21 data card for my GNS430W. I tried updating mine for my planned training at IFR6 (in 3 days!) but that corrupted the card. Anyone have a spare card available? They are 2+ weeks lead time everywhere I looked.

The most recent GPS update nuked BOTH of my terrain cards (010-10201-21). I have also heard from other Mooney drivers that this recent update killed theirs as well. The second card was seen for a moment, but as soon as it started to push data, it disappeared and hasn't been readable since - both are corrupted and cause my GNS-530W to crash on boot.I have one more spare brand new card, and am really reluctant to put it in my programmer to update. Without the terrain card, my GNS530W boots up just fine, except for the missing GPS data.

Has anyone else had a problem here? I'm thinking that this is a Garmin issue at this point.

There was a new terrain database issued a few months ago that has caused problems with improperly loading on multiple systems/navigators. Garmin has issued some bulletins on how to fix this issue and get it properly installed. I would search the garmin "Aviation Alerts" page using GNS as a key word. I suspect you'll find some help. If not, then call Garmin tech support and they'll get you through it.

I had something happen with the terrain card on my GNS 430W after the last update. The obstacles worked but both the main and airport terrain databases had integrity errors. I tried reloading the card and after that obstacles and the main terrain databases worked, but the airport terrain database still had an integrity error. The unit otherwise works fine. I contacted Garmin support and they suggested reloading using the old method (where you download an executable file) and that made no difference. They then had me see if it would load with the NavData card removed. That made no difference. Support is stumped and kicked it to engineering.

I am having same issue after latest terrain and obstacle update. First both were bad so I reinstalled obstacle and terrain databases, now obstacle is fine but terrain integrity error persists.

Here we go again with corrupted data cards. Been a week but I updated the IFR card, then went to update the TAWS/Terrain card and FlyGarmin quit. I have tried this on both Mac and Windows machines. Same issue about 18 months ago with a card - no claim of responsibility - but they did send me a new card (different plane). I last updated updated these cards in March when I picked up the plane in FL, then the plane went in for upgrades so no updates until June. Now, I get the yellow text of non-happiness when I insert the card in the right slot of the 530W.

The app shuts quits spontaneously and brings up the error screen on my Mac when I insert the terrain card now. There was no indication that anything was happening to the card the first time I tried to update it. No flashing lights, no nothing.

They didn't tell me to completely exit the flygarmin updater, but they did say to only select one card at a time for programming. I always thought the application acted squirrely when I checked both boxes anyway. I asked if this meant that there was a problem with the programming application and they said, "No, this is just considered a best practice." I thought this explanation strange. Why would there be a feature of the programming application that they recommend you not to use if you complain that it killed your card if the feature wasn't problematic?

It appears that after a card is corrupted, there is no way to recover it. Did you check both update boxes to update both cards and the terrain card became corrupted, or did you do them one at a time and still get the corruption?

I update them both at the same time, so I probably selected both and did them back-to-back. But it wasn't until a day or more later that I put the cards back in the plane and discovered the problem, so I didn't take close note of what procedure I used for the update.

I am trying to create a view out of the GP database that I can use to import into a data model for Power BI for reporting on inventory layers. My background is in working with relational databases, not in GP or accounting.

I want the QTYRECVD and QTYSOLD out of the work table (IV10200), but I also want the DOCDATE (for the date sold) out of the detail (IV10201), so I can determine when each layer was sold. So far, every way I can think of to join these two tables in the T-SQL for the view results in duplication. For example, if Receipt 1 brought in 20 items on 1/1/2018, and these items were sold on two different dates--say, 2 items on 2/1/2018 and 10 on 3/1/2018--then I should have received a total of 20, sold a total of 12, and have 8 on hand (assuming no adjustments, which is why I get the QTYSOLD out of the header, which will include adjustments and should make my on-hand number accurate). The trouble is, I haven't found a way to join these two tables that won't result either in two copies of the header (one for each of the two sales in the detail table), which makes it look as though I've received 40 instead of 20, or (if, for example, the two sales happened to be on the same date) that is falsely eliminating some of the detail records, so it looks like I received 20 but only sold 2.

3a8082e126