 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Developer Toolkits / March 2005Access System Error - No grp for this
Application Error. The memory could not be "written" There isn't a disc. grp for this so I thought I'd try here first, since system developers like myself tend to hang out here. I'm getting this error when I logon to a shared Access application. When ? Only on older PC's. Not always the same PC's, rarely at the same time. Works MOST of the time. May not work one day, next day is fine. May not have any problems at all for days, even a week. If I use a copy of the application, and run it ? NEVER a problem ! I saw something on the web saying it may be bad memory, I'm looking into that since it is only the older PC's that get this. My first thought was .dll mismatches, but I couldn't find any. Bad memory gives the same type of errors. Any other suggestions ? Thanks. Bad memory chip is a possibility, but as you said you could duplicate this on other machines (albeit older machines). > If I use a copy of > the application, and run it ? NEVER a problem ! What do you mean by this? Please explain exactly how you're running a copy of the application. Running it locally? Is your application split with FE/BE? What version of Access? Are all service packs installed? The .mdb file may possibly be corrupt needing a compact/repair or even a decompile. You may even import all objects to a freshly created blank .mdb. HTH, Immanuel Sibero > Application Error. > The memory could not be "written" [quoted text clipped - 21 lines] > > Thanks. Hi Immanuel, Copy: If a PC is failing, I can copy db.mdb to db2.mdb and use it. Or I can use a previous version. The next day, the same version that didn't work, will work. Runs off of a network drive, fe/mdb-be/sqlsrv - linked tables. Version: Acc 2k, all service packs. Before a release, mdb is comp/repair. A corruption problem would affect all, or at least the same PC's, all the time. Since this posting 2 days ago, no reported problems. Thanks for any help. This has been going on since January. > Bad memory chip is a possibility, but as you said you could duplicate this > on other machines (albeit older machines). [quoted text clipped - 41 lines] > > > > Thanks. Stuart, > > > I'm getting this error when I logon to a shared Access application. One important question I failed to ask: Does each user run a separate copy of the Access FE? If not, they should. I would put a copy on each user's machine and each user should run that local copy. Immanuel Sibero > Hi Immanuel, > [quoted text clipped - 55 lines] > > > > > > Thanks. Immanuel, Ok. I'll have to answer to my client as to why. They were running for years with the shared app method. This started after we upsized from Acc to SQL. So blaming this as the cause is ok, but I'll have to answer the question "why" since it worked before. Thanks, again. > Stuart, > [quoted text clipped - 77 lines] > > > > > > > > Thanks. Hi Stuart, Fair enough. This is heavily documented. http://allenbrowne.com/ser-01.html http://www.granite.ab.ca/access/splitapp/index.htm Granted, there is no guarantee that your problem was caused by not splitting the database. If you havent already, check out information re: mdb corruptions at the following: http://www.granite.ab.ca/access/corruptmdbs.htm One of the symptoms listed here sounds like what you have (worth a look) - Application error: Memory Write error: http://www.granite.ab.ca/access/corruption/symptoms.htm HTH, Immanuel Sibero > Immanuel, > [quoted text clipped - 86 lines] > > > > > > > > > > Thanks. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.