Question about memory allocation

boaz · Joined: 04 Oct 2007 Posts: 259

Hi,

Please take a look at the following codes:

10 Dim My_Recordset As ADODB.Recordset
20 Set My_Recordset = New ADODB.Recordset
30 My_Recordset.Open [This and That]
40 My_Recordset.Close
50 Set My_Recordset = New ADODB.Recordset
60 My_Recordset.Open [This and That]
70 My_Recordset.Close
80 Set My_Recordset = Nothing

I have 2 "Set My_Recordset = New ADODB.Recordset" statements.

Would you tell me what kind of problem (if any) I will get please?

--
>There is no answer.
> There has not been an answer.
> There will not be an answer.
> That IS the answer!

Archived from group: microsoft>public>vb>enterprise

Val · Joined: 04 Oct 2007 Posts: 3

>-----Original Message-----
>Hi,
>
>Please take a look at the following codes:
>
>10 Dim My_Recordset As ADODB.Recordset
>20 Set My_Recordset = New ADODB.Recordset
>30 My_Recordset.Open [This and That]
>40 My_Recordset.Close
>50 Set My_Recordset = New ADODB.Recordset
>60 My_Recordset.Open [This and That]
>70 My_Recordset.Close
>80 Set My_Recordset = Nothing
>
>I have 2 "Set My_Recordset = New ADODB.Recordset"
statements.
>
>Would you tell me what kind of problem (if any) I will
get please?
>
>
>
>--
>>There is no answer.
>> There has not been an answer.
>> There will not be an answer.
>> That IS the answer!
>
>
>.
>

No problem (that I know of). After line 50, you loose the
reference to the first Recordset object, but this isn't a
problem for VB. As soon as VB detects that an object isn't
referenced anymore, it will destroy that object and
reclaim the memory allocated for it. Although you don't
need to explicitly set the variable My_Recordset to
Nothing, calling Close when you've finished with the
Recordset is necessary in order to avoid resource leaks.
HTH,
Val

boaz · Joined: 04 Oct 2007 Posts: 259

Thanks for the info. I have another question.

If I add the following line, will it create any problem?

45 Set My_Recordset = Nothing

"Val" wrote in message$e6c0d570$a301280a@phx.gbl...
>
> >-----Original Message-----
> >Hi,
> >
> >Please take a look at the following codes:
> >
> >10 Dim My_Recordset As ADODB.Recordset
> >20 Set My_Recordset = New ADODB.Recordset
> >30 My_Recordset.Open [This and That]
> >40 My_Recordset.Close
> >50 Set My_Recordset = New ADODB.Recordset
> >60 My_Recordset.Open [This and That]
> >70 My_Recordset.Close
> >80 Set My_Recordset = Nothing
> >
> >I have 2 "Set My_Recordset = New ADODB.Recordset"
> statements.
> >
> >Would you tell me what kind of problem (if any) I will
> get please?
> >
> >
> >
> >--
> >>There is no answer.
> >> There has not been an answer.
> >> There will not be an answer.
> >> That IS the answer!
> >
> >
> >.
> >
>
> No problem (that I know of). After line 50, you loose the
> reference to the first Recordset object, but this isn't a
> problem for VB. As soon as VB detects that an object isn't
> referenced anymore, it will destroy that object and
> reclaim the memory allocated for it. Although you don't
> need to explicitly set the variable My_Recordset to
> Nothing, calling Close when you've finished with the
> Recordset is necessary in order to avoid resource leaks.
> HTH,
> Val

Bob Butler · Joined: 04 Oct 2007 Posts: 2047

"boaz" wrote in message@TK2MSFTNGP09.phx.gbl
> Thanks for the info. I have another question.
>
> If I add the following line, will it create any problem?
>
> 45 Set My_Recordset = Nothing

No, it will not create a problem. Since line 50 sets 'My_Recordset' to
something else it is not necessary but it does no harm beyond possibly
requiring a few extra CPU cycles during execution.