Ms Access Runtime Error 7878
Social Groups Pictures & Albums Members List Calendar Search Forums Show Threads Show Posts Tag Search Advanced Search Find All Thanked Posts Go to Page... Thread Tools Rate Thread Display Modes 09-07-2008, 08:07 AM #1 Mikahell Registered User Join Date: Sep 2008 Posts: 3 Thanks: 0 Thanked 0 Times in 0 Posts Error 7878 (data has been changed) Hi all, I'm having this problem with error 7878, which from other posts I have seen would be an error occuring when 2 users edit the same data at the same time. However, I'm currently developping so I am the only one in the database, always. I'm trying to send the value of the primary key in some form to a parent form which will receive it in a foreign key field. On my first described form, when I click a button, it closes the form and send in a global variant the value of the textbox representing the primary key, so the other form can receive it. It works great, unless I edit data in the first form and exit the form without firstly clicking the record selector control to save the modified data (generates error 7878). I got desperate and tried various things to force access to save the current record before closing the form, but the error persists. I have tried including in my close button click's event procedure combinations of all the following, but the error still persists : DoCmd.Save RunCommand acCmdSaveRecord Me.Requery Me.Refresh DbEngine.Idle dbRefreshCache Sleep(1000) From what I understand, the saving of the record really happens (one would hope, after calling so many kind of save functions) but it "happens" only after the button's event is finished... But since the form closes in the button's click, the data is "being saved but not really completed". If I can be clearer, I think that the form's record is only saved once all user-functions stack are done and that the focus is sent back to the form, or so... I suppose it works this way, and I wanted to know if there's a kind of method to pause the execution of the current event and force the refreshing of the form (like a multi-threaded app would wait until one process is completely finished before continuing another task), so that the form would really get to "Me.Dirty = False" state before the form closes, avoiding error 7878. I've heard multithreading in access is impossible, but I don't believe it, since I have seen a user progressbar control (wish I had the code -_-) that does a loop of actions and increments the progressbar's fil
Question Need help? Post your question and get tips & solutions from a community of 418,595 IT Pros & Developers. It's quick & easy. Run time error, "The data has been changed." P: n/a Bill Short Hello All, I have a popup form that is called from a command button on the main form. The main form's data source is tblA. The data source for the popup form is a query that is based on tblA. The OnClose event of the popup attempts to change data in a text box on the main form if certain changes have been made on the popup. Because both use the same data source I have tried saving the record before attempting to make the changes, I have tried refeshing both the popup and the main form. http://www.access-programmers.co.uk/forums/showthread.php?t=156464 I have tried all of these save attempts in the following places: My own exit command button, form unload event, form deactivate event, form close event. I continue to get the "runtime error '-2147352567 (80020009)' The data has been changed." The part that boggles my mind the most is that if I setup a save button on the popup form and click that after making my changes and then close the popup it works perfectly. If I put in a break in the code and step through https://bytes.com/topic/access/answers/192176-run-time-error-data-has-been-changed it, it works perfectly. Any help would be greatly appreciated. Bill Newtown PA Nov 12 '05 #1 Post Reply Share this Question 2 Replies P: n/a Albert D. Kallal I have a LOT of forms that call other forms based on the same data source. The trick is simply to make sure RIGHT BEFORE you launch another form, you force a disk write. That way, the current record is written to disk, and then here is NO pending write. You then simply launch that other form, in your case the popup. So. me.Refresh .....code to launch popup ..... popup form may modify data. .... popup form close We are back. The above should just work fine. So, the real "trick" is to ALWAYS write out the current record to disk RIGHT BEFORE you popup, or leave to another form. While I always use me.Refresh, many of the more experienced developers here have pointed out that the following code is better: if me.Dirty = True then me.Dirty = false endif -- Albert D. Kallal (MVP) Edmonton, Alberta Canada No************@msn.com http://www.attcanada.net/~kallal.msn Nov 12 '05 #2 P: n/a Bill Short Albert, Thanks for the reply. I already run a save on the main form before opening the popup. But that is not where my error occurs. It happens when returning from the popup (if changes have been made on the popup). Have you ever seen this situation where there is a runtime error but when you put in a code break and step through there is no error? Thanks, Bill ***
Custom Search UtterAccess Forums>Microsoft® Access>Access Q and A http://www.utteraccess.com/forum/run-time-error-7878-t1959769.html Run Time Error 7878 Forum HomeSearchHelpUA Messages|-- UtterAccess.com NewsAccess Knowledge Center|-- Access Code Archive|-- Access Knowledgebase / FAQ|-- http://www.solvusoft.com/en/errors/runtime-errors/microsoft-corporation/microsoft-access/7878-access-error-7878/ Access TutorialsMicrosoft® Access|-- Local Access User Groups (AUGs)|-- Interface Design|-- Access Q and A|-- Access Tables + Relationships|-- Access ms access Queries|-- Access Forms|-- Access Reports|-- Access Macros|-- Access Modules|-- Access Date + Time|-- Access Errors + Error Handling|-- Access Built-in Functions|-- Access Searching + Data Mining|-- Access Records|-- Access Security|-- Access Automation|-- Access Database Container|-- Tool bars, Menu bars ms access runtime + Ribbon|-- Access Services (Web Databases)|-- Access Data Access Pages (Deprecated)|-- Access Data Projects - ADP|-- Access Runtime, Packaging & DeploymentAnd More...|-- Microsoft SQL Server|-- SQL Server Reporting Services|-- Microsoft SharePoint|-- Microsoft Internet Explorer|-- Visual Basic 6 and Earlier|-- Visual Basic 2003 and Later|-- ASP and VBScript|-- Web Development|-- PHP, Perl, MySQL and Postgres|-- Other Database Engines|-- BI Tools and Applications|-- JAVA and C#|-- GraphicsMicrosoft® Office|-- Microsoft Excel|-- Microsoft Excel FAQs|-- Microsoft Word|-- Microsoft Outlook|-- Microsoft PowerPoint|-- Microsoft FrontPage/Exp. Web|-- Other Microsoft ProductsPC|-- Network Issues|-- Q & A - Hardware|-- Q & A - Software|-- Q & A - Other PC|-- Virus + Security DiscussionUtterAccess Odds and Ends|-- General Chat|-- Q & A - UtterAccess.com Forums
DriverDoc WinSweeper SupersonicPC FileViewPro About Support Contact Errors Troubleshooting › Runtime Errors › Microsoft Corporation › Microsoft Access › Error 7878 How To Fix Microsoft Access Error 7878 Error Number: Error 7878 Error Name:Access Error 7878 Error Description: Error 7878: Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience. Developer:Microsoft Corporation Software:Microsoft Access Applies to:Windows XP, Vista, 7, 8 Download NowWinThruster 2015 - Scan your PC for computer errors. Compatible with Windows 10, 8, 7, Vista, XP and 2000 Symptoms of Error 7878 "Error 7878" appears and crashes the active program window. Your PC frequently crashes with Error 7878 when running the same program. “Access Error 7878” is displayed. Windows runs sluggishly and responds slowly to mouse or keyboard input. Your computer periodically “freezes” for a few seconds at a time. These 7878 error messages can appear during program installation, while a Microsoft Corporation-related software program (eg. Microsoft Access) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your 7878 error occurs is a critical piece of information in troubleshooting the problem. Causes of Error 7878 Corrupt download or incomplete installation of Microsoft Access software. Corruption in Windows registry from a recent Microsoft Access-related software change (install or uninstall). Virus or malware infection that has corrupted Windows system files or Microsoft Access-related program files. Another program maliciously or mistakenly deleted Microsoft Access-related files. Runtime Errors such as “Error 7878” can be caused by a variety of factors, so it is important that you troubleshoot each of the possible causes to prevent it from recurring. Runtime Errors Knowledgebase Article ID: 121185 Article Author: Jay Geater Last Updated: 19-07-2016 Popularity: star rating here Download NowError Fix Learn More Tweet Recommendation: Scan your PC for computer errors. How To Fix Microsoft Access Error 7878 Below is a list of troubleshooting steps to resolve your Error 7878 problems. These troubleshooting steps get progressively more difficult and time consuming, so we strongly recommend attempting them in ascending order to avoid unnecessary time and effor