Size limitation warning on Personal Geodatabases

Idea created by jmbishop on Feb 23, 2015
    • jmbishop
    • Hornbydd
    • kcohen
    It would be great if a warning was generated early on when you are copying/exporting a feature class from a file geodatabase to a personal geodatabase if the size limitation will be exceeded. Presumablely since it is already in a geodatabase, the size is known and since the size limit on personal geodatabases is static, this would be a great feature for when working with large datasets. It is rather annoying to have to wait 20-30minutes for the feature class to database tool to run only to find out that its too big. (Alternatively, there could be a way to split the data between two personal geodatabases, but I don't know if this would be possible.)