Fill out some information on the index metadat in the table definition.
expand/clarify information related to index entry pages.
Fill out some more details on property blocks.
filled in a few more bits in the table def.
Add notes about text index sort order.
fill out some details about the database definition page (page 0) and the text
code page/sort order info.
add some info about complex columns (access v2007+).
Merge remote-tracking branch 'upstream/master'
t
gitignore update
merge with master
MDB_DEPRECATED redefined, Constructor MACRO, generate_table_schema changed to not static, date_fmt to ISODate

__attribute__ does not exist in Visual Studio. Therefore replaced wherever it appeared with a macro:
Redefines MDB_DEPRECATED to support Visual Studio
Define a Constructor MACRO so that __attribute__((constructor/destructor)) behavior is achieved in Visual Studio.

Just using generate_table_schema through mdb_print_schema deletes the purpose of a very good tool. generate_table_schemas is a rewrite of generate_table_schema but sends the data to a char* instead of FILE*. There is NO fmemopen() or similar in Visual Studio, so there is NO way to access memory through a FILE* except for first writing to the disk and then reading from the disk in memory.

I cannot suggest how to handle the case when td == 0 for the dates. The databases I work with often have just 00:00:00 in the DateTime column which is not consistent with the rest of the column either, but I have to deal with it somehow.

Leaving void* where char* is needed as a function parameter returns a compilation error in Visual Studio.
Memory leak wrong fix

Free col->sargs
Note this patch causes SEGV
Memory leak fix

Free the col->sargs
Fixed password decoding

Thanks Jimmy Taker compilation warning.
__attribute__ change into macro

Makes it easier to port to another compiler.
Thanks Jimmy Taker
Memory leak fix

Need to free previous backend name when changing it.
Memory leak fix

Free temporary variable in mdb_print_indexes
Fix build if yacc is missing
Changed the gmdb warning when SQL is disabled

--enable-sql option is no more.