
Fatal Exception in deplayer-only
Fatal Exception in deplayer-only
Hi. Not DE-savvy, so please forgive me. We recently migrated, thanks to one of DE's brilliant associates, over to LE9 from from LE 6.53. One niggle that we can't seem to fathom: when running certain procedures in deplayer, we get a Fatal Exception: Access Violation, and we are kicked out. I believe this is to do with memory? The strange thing is, when running the same procedures through Developer, they work perfectly. Stranger still - a single colleague of mine, running the same version of Windows, is able to run said procedures through deplayer.... Any ideas why these would work through Developer and not player, and why they do seem to work through player for a single user? Thanks in advance.
Re:Fatal Exception in deplayer-only
Are you running the DEPLAYER that is shipped with Developer.
We have seen sometimes that doesn't work when Developer does and the full player works. The Player shipped with Developer is more a test version (even though eventually it will be a full part of the package) to test application on how they will work in player when you develop.
The problem is sharing of files and settings between Developer and Player.
Which version are you using?
Re:Re:Fatal Exception in deplayer-only
Hello. Thank you for your response. I believe we are running the most up-to-date version of each - 9.0.0.6835. We have only very recently downloaded and installed them. What I can't seem to work out is why these procedures work through player on one particular machine, but crash on all others. We have 7 users, all running the same version of player. 6 out of 7 crash - but one seems to work perfectly. The machine it is working on is running the same version of Windows (11). There's nothing obviously different about it. Most peculiar!