> In fact when i put the read-only bit attribute in the file on my computer
when i upload this
> file on Pose (with "load databases" or "sync") the OS (3.5.2) occure an
error (i didn't try
> on my device). The begining of the file (a part of the header) is
uploaded, my
> application see the name,
I found my problem, thank you.
In fact when i put the read-only bit attribute in the file on my computer when i
upload this file on Pose (with "load databases" or "sync") the OS (3.5.2) occure an
error (i didn't try on my device). The begining of the file (a part of the header) is
uploaded, my
> I just changed the byte 0x21 from 0x00 to 0x02 in the pdb file, with a
Hexa editor. Nothing else.
That's the right thing to do. Can you do a binary diff of the original and
modified files to verify that your hex editor is working properly? Perhaps
you're unintentionally inserting the byte 0x21
>How are you setting this bit? Are you using a binary/hex editor?
I just changed the byte 0x21 from 0x00 to 0x02 in the pdb file, with a Hexa editor.
Nothing else.
I do:
DmDatabaseInfo to read the attr UInt16.
DmOpenDatabase to open the database with dmModeReadOnly if the Read-Only bit is set
> When i set the Read-Only bit attribute in a .pdb file, when i use
DmGetAppInfoID the return is
> null or there are an AppInfo block in the database. I have this problem
only with the Read-Only
> bit and not with others.
You should be able to access the app info block of a database with the
dmHd
