Hi all,
What do people regard as the best practice with respect to freeing object references when you're done with them? Some people I've worked with in the past suggested that if you create an object with "New" then you should free/set it to nothing when you're finished with it, regardless of whether it's about to go out of scope or not.
In a simple example:
Private Sub DoSomething()
Dim fForm As New frmMain
fForm.Show()
'... do some things with this form
fForm.Close()
fForm = Nothing
End Sub
Is the "fForm = Nothing" necessary if garbage collection will take care of the object reference once the procedure completes? What is the best practice here?
Thanks!
Mike
12  2636 
You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for garbage
collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com... Hi all,
What do people regard as the best practice with respect to freeing object
references when you're done with them? Some people I've worked with in the
past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether
it's about to go out of scope or not.
In a simple example:
Private Sub DoSomething()
Dim fForm As New frmMain
fForm.Show()
'... do some things with this form
fForm.Close()
fForm = Nothing
End Sub
Is the "fForm = Nothing" necessary if garbage collection will take care
of the object reference once the procedure completes? What is the best
practice here?
Thanks!
Mike
I meant, when DoSomething exits, not exists...
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for garbage
collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com... Hi all,
What do people regard as the best practice with respect to freeing
object references when you're done with them? Some people I've worked with in
the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether
it's about to go out of scope or not.
In a simple example:
Private Sub DoSomething()
Dim fForm As New frmMain
fForm.Show()
'... do some things with this form
fForm.Close()
fForm = Nothing
End Sub
Is the "fForm = Nothing" necessary if garbage collection will take care
of the object reference once the procedure completes? What is the best
practice here?
Thanks!
Mike
What about if you are repeatedly creating a new reference to an object using
the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for garbage
collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com... Hi all,
What do people regard as the best practice with respect to freeing
object references when you're done with them? Some people I've worked with in
the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether
it's about to go out of scope or not.
In a simple example:
Private Sub DoSomething()
Dim fForm As New frmMain
fForm.Show()
'... do some things with this form
fForm.Close()
fForm = Nothing
End Sub
Is the "fForm = Nothing" necessary if garbage collection will take care
of the object reference once the procedure completes? What is the best
practice here?
Thanks!
Mike
I assume you only have one of these in a loop (otherwise it won't compile).
I would assume on the next iteration of the loop that lstSutff variable
would have gone out of scope, ready for garabase collection.
Greg
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for garbage
collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com... Hi all,
What do people regard as the best practice with respect to freeing object references when you're done with them? Some people I've worked with in
the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of
whether it's about to go out of scope or not.
In a simple example:
Private Sub DoSomething()
Dim fForm As New frmMain
fForm.Show()
'... do some things with this form
fForm.Close()
fForm = Nothing
End Sub
Is the "fForm = Nothing" necessary if garbage collection will take
care of the object reference once the procedure completes? What is the best
practice here?
Thanks!
Mike
After rereading, I think you meant to type something more akin to this:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
Again, I don't see any need to set it to nothing.
Greg "Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for
garbage collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com...
> Hi all,
>
> What do people regard as the best practice with respect to freeing
object references when you're done with them? Some people I've worked with
in the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether it's about to go out of scope or not.
>
> In a simple example:
> Private Sub DoSomething()
> Dim fForm As New frmMain
> fForm.Show()
> '... do some things with this form
> fForm.Close()
> fForm = Nothing
> End Sub
>
> Is the "fForm = Nothing" necessary if garbage collection will take care of the object reference once the procedure completes? What is the
best practice here?
>
> Thanks!
> Mike
Sorry, I'm an idiot!. My sample should have been:
Dim lstStuff AS ListViewItem
lstStuff = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
lstStuff = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Do I need to set lstStuff to NOTHING in this example?
"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I assume you only have one of these in a loop (otherwise it won't
compile). I would assume on the next iteration of the loop that lstSutff variable
would have gone out of scope, ready for garabase collection.
Greg
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for
garbage collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com...
> Hi all,
>
> What do people regard as the best practice with respect to freeing
object references when you're done with them? Some people I've worked with
in the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether it's about to go out of scope or not.
>
> In a simple example:
> Private Sub DoSomething()
> Dim fForm As New frmMain
> fForm.Show()
> '... do some things with this form
> fForm.Close()
> fForm = Nothing
> End Sub
>
> Is the "fForm = Nothing" necessary if garbage collection will take care of the object reference once the procedure completes? What is the
best practice here?
>
> Thanks!
> Mike
What about if you are repeatedly creating a new reference to an object using
the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for garbage
collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com... Hi all,
What do people regard as the best practice with respect to freeing
object references when you're done with them? Some people I've worked with in
the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether
it's about to go out of scope or not.
In a simple example:
Private Sub DoSomething()
Dim fForm As New frmMain
fForm.Show()
'... do some things with this form
fForm.Close()
fForm = Nothing
End Sub
Is the "fForm = Nothing" necessary if garbage collection will take care
of the object reference once the procedure completes? What is the best
practice here?
Thanks!
Mike
I assume you only have one of these in a loop (otherwise it won't compile).
I would assume on the next iteration of the loop that lstSutff variable
would have gone out of scope, ready for garabase collection.
Greg
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for garbage
collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com... Hi all,
What do people regard as the best practice with respect to freeing object references when you're done with them? Some people I've worked with in
the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of
whether it's about to go out of scope or not.
In a simple example:
Private Sub DoSomething()
Dim fForm As New frmMain
fForm.Show()
'... do some things with this form
fForm.Close()
fForm = Nothing
End Sub
Is the "fForm = Nothing" necessary if garbage collection will take
care of the object reference once the procedure completes? What is the best
practice here?
Thanks!
Mike
After rereading, I think you meant to type something more akin to this:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
Again, I don't see any need to set it to nothing.
Greg "Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for
garbage collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com...
> Hi all,
>
> What do people regard as the best practice with respect to freeing
object references when you're done with them? Some people I've worked with
in the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether it's about to go out of scope or not.
>
> In a simple example:
> Private Sub DoSomething()
> Dim fForm As New frmMain
> fForm.Show()
> '... do some things with this form
> fForm.Close()
> fForm = Nothing
> End Sub
>
> Is the "fForm = Nothing" necessary if garbage collection will take care of the object reference once the procedure completes? What is the
best practice here?
>
> Thanks!
> Mike
Sorry, I'm an idiot!. My sample should have been:
Dim lstStuff AS ListViewItem
lstStuff = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
lstStuff = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Do I need to set lstStuff to NOTHING in this example?
"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I assume you only have one of these in a loop (otherwise it won't
compile). I would assume on the next iteration of the loop that lstSutff variable
would have gone out of scope, ready for garabase collection.
Greg
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl... You don't need to set it to nothing. When DoSomething exists, all the
variables defined in it go out of scope and become eligible for
garbage collection.
"Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
news:6F**********************************@microsof t.com...
> Hi all,
>
> What do people regard as the best practice with respect to freeing
object references when you're done with them? Some people I've worked with
in the past suggested that if you create an object with "New" then you should
free/set it to nothing when you're finished with it, regardless of whether it's about to go out of scope or not.
>
> In a simple example:
> Private Sub DoSomething()
> Dim fForm As New frmMain
> fForm.Show()
> '... do some things with this form
> fForm.Close()
> fForm = Nothing
> End Sub
>
> Is the "fForm = Nothing" necessary if garbage collection will take care of the object reference once the procedure completes? What is the
best practice here?
>
> Thanks!
> Mike
Well, first of all, it depends :P
In your example...no, you don't need to set the value to Nothing....although..in
a situation I was just in, I did need to call
System.Runtime.InteropServices.Marshal.ReleaseComO bject() to release a GroupWise
object when I used it in ASP.Net. But that's another story...other than
unmanaged objects, you don't have to worry about free'ing the references. The
garbage collection is pretty good at what it does for every day tasks.
Mythran
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:s2****************@twister.nyroc.rr.com... Sorry, I'm an idiot!. My sample should have been:
Dim lstStuff AS ListViewItem
lstStuff = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
lstStuff = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Do I need to set lstStuff to NOTHING in this example?
"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I assume you only have one of these in a loop (otherwise it won't
compile). I would assume on the next iteration of the loop that lstSutff variable
would have gone out of scope, ready for garabase collection.
Greg
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl...
> You don't need to set it to nothing. When DoSomething exists, all the
> variables defined in it go out of scope and become eligible for garbage > collection.
>
> "Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
> news:6F**********************************@microsof t.com...
> > Hi all,
> >
> > What do people regard as the best practice with respect to freeing
object
> references when you're done with them? Some people I've worked with in the
> past suggested that if you create an object with "New" then you should
> free/set it to nothing when you're finished with it, regardless of
whether > it's about to go out of scope or not.
> >
> > In a simple example:
> > Private Sub DoSomething()
> > Dim fForm As New frmMain
> > fForm.Show()
> > '... do some things with this form
> > fForm.Close()
> > fForm = Nothing
> > End Sub
> >
> > Is the "fForm = Nothing" necessary if garbage collection will take
care > of the object reference once the procedure completes? What is the best > practice here?
> >
> > Thanks!
> > Mike
>
>
Well, first of all, it depends :P
In your example...no, you don't need to set the value to Nothing....although..in
a situation I was just in, I did need to call
System.Runtime.InteropServices.Marshal.ReleaseComO bject() to release a GroupWise
object when I used it in ASP.Net. But that's another story...other than
unmanaged objects, you don't have to worry about free'ing the references. The
garbage collection is pretty good at what it does for every day tasks.
Mythran
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:s2****************@twister.nyroc.rr.com... Sorry, I'm an idiot!. My sample should have been:
Dim lstStuff AS ListViewItem
lstStuff = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
lstStuff = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Do I need to set lstStuff to NOTHING in this example?
"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I assume you only have one of these in a loop (otherwise it won't
compile). I would assume on the next iteration of the loop that lstSutff variable
would have gone out of scope, ready for garabase collection.
Greg
"Clark Stevens" <cy*********@hotmail.com> wrote in message
news:rI*******************@twister.nyroc.rr.com... What about if you are repeatedly creating a new reference to an object
using the same object variable each time? For example:
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "First ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Dim lstStuff AS ListViewItem = New ListViewItem
lstStuff.Text = "Another ListviewItem"
listview1.Items.Add(lstStuff)
lstStuff = Nothing
Is it necessary to set lstStuff to nothing before creating a New
reference?
"Marina" <so*****@nospam.com> wrote in message
news:el**************@TK2MSFTNGP09.phx.gbl...
> You don't need to set it to nothing. When DoSomething exists, all the
> variables defined in it go out of scope and become eligible for garbage > collection.
>
> "Mike Eaton" <Mi*******@discussions.microsoft.com> wrote in message
> news:6F**********************************@microsof t.com...
> > Hi all,
> >
> > What do people regard as the best practice with respect to freeing
object
> references when you're done with them? Some people I've worked with in the
> past suggested that if you create an object with "New" then you should
> free/set it to nothing when you're finished with it, regardless of
whether > it's about to go out of scope or not.
> >
> > In a simple example:
> > Private Sub DoSomething()
> > Dim fForm As New frmMain
> > fForm.Show()
> > '... do some things with this form
> > fForm.Close()
> > fForm = Nothing
> > End Sub
> >
> > Is the "fForm = Nothing" necessary if garbage collection will take
care > of the object reference once the procedure completes? What is the best > practice here?
> >
> > Thanks!
> > Mike
>
>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Geert-Pieter Hof |
last post by:
Hello,
I have written an application in Visual Basic 6.0 Professional SP5 that
reads data from an Excel workbook by using ADO. When I close the
application, I get the error:
'The instruction...
|
by: DD |
last post by:
I am testing a software with Wise Installer on Win 98
In a field i recieve this error #
I do not recieve this error in this field when i test on Win2k or xp
the calculation is as follows
...
|
by: Rich Wallace |
last post by:
Hi all,
I have a VB app that runs and manages individual XLS files within a single
COM object. Upon processing the final fie, I attempt to close out the EXCEL
object and release it using...
|
by: Joe Van Dyk |
last post by:
Is there some rule of thumb about when to use pointers to an object and
when to use a reference* to an object when a class needs to have objects
as data members?
Example:
class A
{
B* b_ptr;...
|
by: Kantha |
last post by:
Hi all,
I have declared an Union as follows
typedef union
{
struct interrupt_bits
{
unsigned char c_int_hs_fs_status : 1,
c_setup_intflag : 1,
|
by: |
last post by:
Hi all,
Coming from the good old VB6 days we were told to always destroy our objects
as follows:-
Dim obj as New MyObject
' do some work with obj
obj = Nothing
I have been doing this in...
|
by: Joe |
last post by:
I am just starting to use Object Oriented PHP coding, and I am seeing
quite often the following (this example taken from a wiki):
$wakka =& new Wakka($wakkaConfig);
What exactly is the =&, and...
|
by: Phil Reynolds |
last post by:
I have Access 2000 and 2003 on my development machine. My client only has
Access 2000. When I develop for this client, I run Access 2000. However, my
code requires that I have the Microsoft Word...
|
by: Astley Le Jasper |
last post by:
Sorry for the numpty question ...
How do you find the reference name of an object?
So if i have this
bob = modulename.objectname()
how do i find that the name is 'bob'
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome former...
|
by: ryjfgjl |
last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
| |
