We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am creating a big application using Banking. Compilation goes fine but in debugging mode, some of the routines gives the error message as Access Violation Problem. When access is gives for that memory locations using MAP command, then the execution will start from beginning causes infinite loop. But some of the routines works from when they moved from Bank 0 to CommonCode area. Not sure why some routines are not working either in Bank 0, Bank 1 or in Common code are. Seeking clarification. Thanks Ashok
Just MAPping that memory as accessible is almost certainly the wrong reaction to those Access Violation errors. What that error is most probably telling you is that your code is crashing headfirst into the barriers between banks that are necessary to allow banked applications to work. Putting holes into those walls is *not* going to make that work. Carefully inspect the context the problem happens in: are you absolutely sure your code isn't doing something that is simply not allowed in banked code?