Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Forms / May 2008

Tip: Looking for answers? Try searching our database.

Memory error after using popup form

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bastet73 - 21 May 2008 21:35 GMT
I have a form with a subform that it used to enter ECOs (Engineering Change
Orders). On the form, when the user selects the option "Type 5" from a
combobox, a popup form is displayed in which the user will enter information
to run two queries. The first query, a select query, takes the user input and
returns records that meet the criteria. The second query is an append query
that takes the information from the select query and appends it into a table
used by the subform on the mainform. The select query is closed upon the
append query completion and the user then clicks the exit command button to
exit the popup and return to the mainform. At this point the subform is
automatically refreshed.

This all works fine; the subform shows the newly appended data. However, I
receive the error "There isn't enough free memory to update the display..."
and some of the text on the form displays weird and the only way to get the
text to display correctly is to exit the database completely and restart it.
This error shows on others PCs as well.

The error seems to be tied into using acDialog for the popup. I use acDialog
to freeze the code until the queries are run so that the refresh of the
subform works. If I remove acDialog and use a command button on the form to
refresh the data I do not get the error.

Is there a way to not have this error come up while using acDialog?

Code on main form:
Private Sub cboEcoType_AfterUpdate()
' Open Component Family entry form if user selects Type 5 from combo box.
Dim strType5 As String
   strType5 = "frmCompFamilyEco"
   
   Me.sbfDwgRevs.SetFocus
   
   If Me.cboEcoType.Value = 5 Then
       DoCmd.OpenForm strType5, , , , , acDialog
       Me.sbfDwgRevs.Requery
       
   End If
   
End Sub

Users  are running either Access 2K with SP3 installed or Access 2003 (error
shows for both). Database is split into a front and back end and run from our
company intranet.

If any other info is needed to help, please let me know.

Thanks!
Klatuu - 21 May 2008 23:17 GMT
You need to apply the HotFix for SP3:

http://support.microsoft.com/kb/945674

Signature

Dave Hargis, Microsoft Access MVP

> I have a form with a subform that it used to enter ECOs (Engineering Change
> Orders). On the form, when the user selects the option "Type 5" from a
[quoted text clipped - 43 lines]
>
> Thanks!
Bastet73 - 22 May 2008 17:38 GMT
The HotFix you pointed me towards is only for Access 2003. I am using Access
2K and am up to date on all patches and fixes for it.

I can try the HotFix on the few at our company that have Office 2003 but most
users are still using Office 2K.

Thanks.

>You need to apply the HotFix for SP3:
>
[quoted text clipped - 5 lines]
>>
>> Thanks!
Klatuu - 22 May 2008 17:48 GMT
Then I don't know what the problem is.
It is always a good idea to state your Access version and Windows version
when posting.
Signature

Dave Hargis, Microsoft Access MVP

> The HotFix you pointed me towards is only for Access 2003. I am using Access
> 2K and am up to date on all patches and fixes for it.
[quoted text clipped - 13 lines]
> >>
> >> Thanks!
Bastet73 - 22 May 2008 18:19 GMT
In my first post, right after the sample of the code I am using, I did state
the two different versions of Access that are being used.

I did not, however, state the version of Windows. Both Win 2K and XP Pro are
being used, both with all the latest patches and HotFixes installed.

>Then I don't know what the problem is.
>It is always a good idea to state your Access version and Windows version
[quoted text clipped - 4 lines]
>> >>
>> >> Thanks!
 
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.