Account depedent application crash

[Beat]

Hi folks -

Here's a puzzling one for the experts:

I have implemented a multi-table solution under FMP7.0.3win for our small company. The thing that is a bit special about it is that it can be synchronized via a central file residing on our office desktop, so my colleague and I (and future collaborators) can use the DB offline while on the road and then sync it when coming back to the office. I got everything to work just fine except for one point:

When the synchronization is done from my laptop, it works fine regardeless of the active account (full-access or custom-defined priviliges). When the sync is done from my colleague's laptop, it also works fine under the full-access account. But when using the limited account, FMP crashes! The sync script and all sub scripts run with full access priviliges. Both laptops have the same OS (WinXPpro SP2, fully updated) and the same version of FMP (7.0.3) and the same cache setting. The crash always happens on the same script step, when importing records from the central DB. BTW, in the same script, records are imported successfully from the same file from several other tables before the fatal import occurs.

Does anybody have a clue what's going on? We have already re-installed FMP on my colleague's laptop but it didn't help. Why wouls account priviliges matter to scripts that have full access anyway? And why is FMP behaving differently on two basically identical setups?

TIA, Beat

[Beat]

Hi folks -

Here's a puzzling one for the experts:

I have implemented a multi-table solution under FMP7.0.3win for our small company. The thing that is a bit special about it is that it can be synchronized via a central file residing on our office desktop, so my colleague and I (and future collaborators) can use the DB offline while on the road and then sync it when coming back to the office. I got everything to work just fine except for one point:

When the synchronization is done from my laptop, it works fine regardeless of the active account (full-access or custom-defined priviliges). When the sync is done from my colleague's laptop, it also works fine under the full-access account. But when using the limited account, FMP crashes! The sync script and all sub scripts run with full access priviliges. Both laptops have the same OS (WinXPpro SP2, fully updated) and the same version of FMP (7.0.3) and the same cache setting. The crash always happens on the same script step, when importing records from the central DB. BTW, in the same script, records are imported successfully from the same file from several other tables before the fatal import occurs.

Does anybody have a clue what's going on? We have already re-installed FMP on my colleague's laptop but it didn't help. Why wouls account priviliges matter to scripts that have full access anyway? And why is FMP behaving differently on two basically identical setups?

TIA, Beat

[Beat]

Hi folks -

Here's a puzzling one for the experts:

I have implemented a multi-table solution under FMP7.0.3win for our small company. The thing that is a bit special about it is that it can be synchronized via a central file residing on our office desktop, so my colleague and I (and future collaborators) can use the DB offline while on the road and then sync it when coming back to the office. I got everything to work just fine except for one point:

When the synchronization is done from my laptop, it works fine regardeless of the active account (full-access or custom-defined priviliges). When the sync is done from my colleague's laptop, it also works fine under the full-access account. But when using the limited account, FMP crashes! The sync script and all sub scripts run with full access priviliges. Both laptops have the same OS (WinXPpro SP2, fully updated) and the same version of FMP (7.0.3) and the same cache setting. The crash always happens on the same script step, when importing records from the central DB. BTW, in the same script, records are imported successfully from the same file from several other tables before the fatal import occurs.

Does anybody have a clue what's going on? We have already re-installed FMP on my colleague's laptop but it didn't help. Why wouls account priviliges matter to scripts that have full access anyway? And why is FMP behaving differently on two basically identical setups?

TIA, Beat

[Beat]

Hmmm. Is there really nobody who wants to come up with a hypothesis, even a wild one?...

[Beat]

Hmmm. Is there really nobody who wants to come up with a hypothesis, even a wild one?...

[Beat]

Hmmm. Is there really nobody who wants to come up with a hypothesis, even a wild one?...

[Beat]

OK. Maybe I'm talking to myself. But for those who are interested, we figured it out. My colleague had installed FMP7 from his own CD which was version v7.0.2 while my installer CD carried v7.0.1. We had both updated to v7.0.3. But apparently, there was still a difference between the two installations! My colleague now un- and reinstalled FMP, but this time from my CD (using his code), updated to v7.0.3 and voila - everything's fine now. We repeated the whole process and it is entirely reproducible. SO BEWARE! You're FMP installation may be different depending on the original installer CD you used. This is pretty severe, IMO.

Beat

[Beat]

OK. Maybe I'm talking to myself. But for those who are interested, we figured it out. My colleague had installed FMP7 from his own CD which was version v7.0.2 while my installer CD carried v7.0.1. We had both updated to v7.0.3. But apparently, there was still a difference between the two installations! My colleague now un- and reinstalled FMP, but this time from my CD (using his code), updated to v7.0.3 and voila - everything's fine now. We repeated the whole process and it is entirely reproducible. SO BEWARE! You're FMP installation may be different depending on the original installer CD you used. This is pretty severe, IMO.

Beat

[Beat]

OK. Maybe I'm talking to myself. But for those who are interested, we figured it out. My colleague had installed FMP7 from his own CD which was version v7.0.2 while my installer CD carried v7.0.1. We had both updated to v7.0.3. But apparently, there was still a difference between the two installations! My colleague now un- and reinstalled FMP, but this time from my CD (using his code), updated to v7.0.3 and voila - everything's fine now. We repeated the whole process and it is entirely reproducible. SO BEWARE! You're FMP installation may be different depending on the original installer CD you used. This is pretty severe, IMO.

Beat