Multiple DayBack files
Posted: Mon Aug 19, 2019 7:08 am
Hi,
I'm having an issue when using multiple DayBack files on one server. The situation:
- my client has 4 physical locations, each with it's own FileMaker file.
- I used to have one DayBack file and we would switch out sources and resources, which worked out ok after some wrangling.
- now, they want to be able to schedule sessions across multiple files and that means they want multiple files open at once.
- I recently re-integrated their solution from the 1-file DayBack 9.x to 4-file DayBack 10.51.
- first, I don't even know if this sort of thing is supported at all, but each file opens up fine on its own.
- however, when you switch from one file to another, the resources from the last-viewed/last-refreshed file populate the 2nd file.
- maybe this has to do with 'xx to CSV' exports? it seems that there is only one set of files for the whole solution...
- I tried messing around with temp file directories, but this produced, expectedly, bad results.
thoughts?
I'm having an issue when using multiple DayBack files on one server. The situation:
- my client has 4 physical locations, each with it's own FileMaker file.
- I used to have one DayBack file and we would switch out sources and resources, which worked out ok after some wrangling.
- now, they want to be able to schedule sessions across multiple files and that means they want multiple files open at once.
- I recently re-integrated their solution from the 1-file DayBack 9.x to 4-file DayBack 10.51.
- first, I don't even know if this sort of thing is supported at all, but each file opens up fine on its own.
- however, when you switch from one file to another, the resources from the last-viewed/last-refreshed file populate the 2nd file.
- maybe this has to do with 'xx to CSV' exports? it seems that there is only one set of files for the whole solution...
- I tried messing around with temp file directories, but this produced, expectedly, bad results.
thoughts?