Developer

One approach to upgrade automation

I just tested one approach to migrating ebase 2.20 data to a future version. It goes like this:

»

Plan for how to implement upgrade from ebase 2.2 to 2.8

Questions we need to address before we build the upgrade path for existing ebase users to get into the next release:

»

How can I delete a bunch of Log entries all at once?

Supplementary documentation on how to delete multiple Log entries quickly.

»

ebasePro 2.12 Administrator's Manual

The Administrator's manual for ebasePro 2.12

»

Theory & Background

information that informs ebase development & documentation

»

Draft road map for porting 2.20 to FM 8

Steps to get to ebase v. 2.8

»

Observations & ideas for transition to .fp7 security model

Modify ebase 2.20 to take advantage of new FileMaker security features.

»