Calendar
| L | M | M | J | V | S | D |
|---|---|---|---|---|---|---|
| « Ene | Mar » | |||||
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | ||
Categorías
- Uncategorized (43)
Últimas entradas
- Mayo 21. 2010: New version 6.1.2 of OrganiZATOR (bug fix)
- Mayo 16. 2010: New version 6.1.1 of OrganiZATOR
- Abril 20. 2010: Error in OrganiZATOR version 6.0.0
- Abril 13. 2010: New OrganiZATOR version 6.0.0
- Marzo 30. 2009: Problem in OrganiZator version 5.8.1
- Marzo 28. 2009: English version of OrganiZator User's Blog
- Marzo 28. 2009: New version 5.8.1 of OrganiZator
- Marzo 20. 2009: New Build of OrganiZator 5.8.0
- Marzo 19. 2009: False positive virus in version 5.8.0 of Zator
- Marzo 17. 2009: New version 5.8.0
Links
Archivos
Clarification on the “critical error in version 5.3.2″
Once investigated the error, we can make clear that it occurs when modifying a Extended field (except the eDir) of an item of dBase that has no content in their field “Note”, and in which the Logbook are equally empty. If you want to change a extended field in an item in the given these circumstances, it is possible to avoid the error by placing previously any content on the “Note” (can be a space character).
The indication “Empty” in the Note field *and* the absence of lines in the Log should be taken as signs that the error will occur when trying to change it’s extended fields!!