Group: Forum Members
Posts: 2K,
Visits: 6.6K
|
It depends. Ideally, you'd have the SF database accessible form both machines. If you can do this, then both machines would just setup the StrataFrame database connection (used by BO Mapper, localization and messaging) to point to the common database.
If that isn't possible, then you have a couple of choices.
1. If you don't need to work with the BO Mapper, localization/messaging (i.e. to setup BOs, define localization/messaging) on one of the machines, then you can just install the StrataFrame db locally, but not use it. I.e. if you have a primary computer that you do most of your work on, it would be connected to the SF database. However you have a secondary laptop that you use less frequently, and you can get away with not setting up BOs, localization or messaging on it, then the laptop would just have a SF database locally (if you can't connect to the StrataFrame db, working with form's at design time is really slow). This is by far the easiest way to go. Most of the work on an app doesn't need the StrataFrame db, so this works out well most of the time.
2. If you need to work on BOs via the BO Mapper, or localization or messaging, and you can't use a common SF db, then you'll need to either move them back and forth between machines.
Note that there has been a request and I believe it is on the list of enhancements (don't quote me on that) to move away from using a db for this meta data and instead move it into the solution folder (as XML? maybe). I'm really hoping this is coming soon. I work remote a lot and usually #1 works well, but there are those times....
|