support routine for index writes

port fix from data.c to mdb_crack_row?()
more tdef4 dissector work in gmdb2
This commit is contained in:
brianb
2004-02-15 06:00:25 +00:00
parent feba3eece6
commit eb2b863b35
5 changed files with 72 additions and 7 deletions

10
HACKING
View File

@@ -467,7 +467,17 @@ Column Type may be one of the following (not complete):
UNKNOWN_0D = 0x0D
REPID = 0x0F /* GUID */
Notes on deleted columns:
If a fixed length column is deleted the offset_F field will contain the values
of the original row definition. Thus is the number of columns on the row does
not match the number in the tdef, the offset_F field could be used to return
the proper data. No idea how multiple column deletions are handled, my instinct
is that Access can only handle a single column deletion event (which may involve
more than one column if new rows have not been added) without touching all the
rows.
Don't know if variable columns work by the same mechanism yet. Stay tuned.
Page Usage Maps
---------------