Valentina is not RAM-based. Your database can be much larger than the installed RAM. However, the more memory Valentina has to work with, the
faster it will be. Starting from v2 Valentina can use RAM-based Databases and Tables.
Valentina database files are the same for 32-bit and 64-bit modes.
Executables - yes are different of course, like for any other application or library. Although MAC OS X allows to pack few branches of code into single file, we tend to provide different archives for 32 and 64 bit executables and ADKs.
DropTable expected to be faster, because when you delete record by record, engine must check constraints and links to delete may be linked records. DropTable() simply delete the table, and try to do fast operation to cleanup links if any.
NO, record is never moved during its lifetime with normal db operations. This can happens only with help of Refactoring commands such as COMPACT or Dump/Load. Note, that refactoring operations always take care about synchronization of all ObjectPtr and BinaryLinks in this case.
ObjectPtr field will be created in the not complete state. Later you must assign a correct Tagret using VObjectPtr.Target property. You may wish to use this tick to be able create tables that have circular reference.