Answer:
We have found that these are occurring with older versions of Operating Systems and of Access. We are trying to narrow down the problem so these errors do not occur. You will generally see the Access Violation causing something to happen in module kernel32.dll, but may see it in something else.
We have also found that the program may crash or just close if you try to convert a database from Access to HanDBase that makes the HanDBase Database have more than 30 fields. Generally if you have 30 fields or less it will convert with no problem. However if you have Date/Time fields in your Access Database and you are converting to a new HanDBase Database it will create two separate fields for every date or time field you have in Access. This could put the number off final fields in HanDBase above 30. To avoid this you can either map only certain columns, being aware that a date or time field will convert to two fields. You can also create the structure of the Database in HanDBase and then Map the fields. Plus if the structure of the HanDBase Database is EXACTLY the same you generally don't have to map and it will convert.
The current remedy is to visit Microsoft's website and make sure you have all the latest updates/maintenance releases for your version of Windows and of Access. You may also want to read Article 137 in our Knowledgebase for more info. We have also discovered that Microsoft's MDAC may be a factor in this and that you may need to get the latest version of that. You can find more info on that and download it from www.microsoft.com/data/. |