Visual Basic 4 Out of Memory Issues

This is a discussion about Visual Basic 4 Out of Memory Issues in the Legacy OS category; I am running two seperate executable files generated from VB4 code. The applications work on machines running win 2000 and xp. I have not tested on NT or server 2000. The applications will not run on Server 2003 or XP for Tablet PC 2005- the only other two OS's that I have access to.

Legacy OS 455 This topic was started by , . Last reply by ,


data/avatar/default/avatar39.webp

3 Posts
Location -
Joined 2005-06-23
I am running two seperate executable files generated from VB4 code. The applications work on machines running win 2000 and xp. I have not tested on NT or server 2000. The applications will not run on Server 2003 or XP for Tablet PC 2005- the only other two OS's that I have access to.
 
The errors I get are common to both applications on both OS's on which the applications will not run.
 
The error messages:
1) "Out of Memory" followed by "Run time error 91: Object Variable or With Block not set.' On debug the line 'Data1.Recordset.Index = SORT$' is indicated as the problem.
2) "Out of Memory" followed by "Run time error 2004: Out of Memory.' On debug the line 'Data1.Refresh' is indicated as the problem.
 
I get the out of memory error once for each time a connection to a databse is made. E.g. at one point a connection is made to 6 seperate databases. I get 6 memory errors followed by the run time error.
 
I am uncertain as to whether this is an OS issue, a data control issue, a case of horrible programming by the original programmer issue or something else.
 
I also get an out of memory error when trying to add a data control to a form. Properties for 'Connect' and 'Database Name' are 'Access' and ' settings.mdb' (shouldn't be an issue). 'Recordset Type = Dynaset'. When I try to set the recordsource property I get the 'Out of Memory' Error.
 
(I have had issues with this code and incorrect use of the 'option explicit' selection- I have no idea if this might also be causing some problems.)
 
Any light that you can shed is greatly appreciated- even if it's just to point me in the right direction to research my own answers!
 

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This subject has been archived. New comments and votes cannot be submitted.
Jun 23
Created
Aug 16
Last Response
0
Likes
3 minutes
Read Time
User User User
Users

Responses to this topic


data/avatar/default/avatar26.webp

690 Posts
Location -
Joined 2004-05-06
For best results, get VB6 or later for Windows 2000 or XP. I found numerous problems with older versions of VB on newer OSs due to big changes in the way the OS works.
 

data/avatar/default/avatar06.webp

760 Posts
Location -
Joined 2001-11-10
I agree I think VB6 is probably the way to go. You shouldn't have to change your code much. It may still be a programming issue, but VB6 might be more explanatory as to what you did wrong whilst coding. I have to assume you're using the Win32 version of your program? You didn't specify and VB4 is 16 or 32 bit. If you aren't already running a 32 bit version I'd make that the first change.

data/avatar/default/avatar06.webp

760 Posts
Location -
Joined 2001-11-10
I have to assume VB4 is service packed and has all available updates? Also the runtimes on the system are the most recent available for vb4?