|
Well, VB6 has nothing to do with VB.NET. I assume that VS in these instances always means VB ? So, I don't see how VS could break VB6 apps
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
VS 6.0 is working but only starting case of form loading or application open or new form opening that time this error is coming how can i solve this error.
|
|
|
|
|
So VS is not working, or your app is not working ?
I repeat - there is no reason I can see for VS2008 to break your VB6 apps. You could try reinstalling whatever runtime it uses, you could google your error, etc.
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
K I will try once reinstall VS 6.0 application.
|
|
|
|
|
Hi
I’m having some problems with a small vb.net application I wrote that inserts data into an Access database.
When I run the application as my self it works comepletely fine on the Windows 2003 server or my desktop XP box.
But when I run it under a local admin account on the Win 2003 server box it does not work and spits our the following error for each insert.
“The field is too small to accept the amount of data you attempted to add.”
The bit I’m having a difficult time understand is why it works under my logon and not a local server logon. There are no domain policies or restrictions in place over the server or local account function on the server. It seems to have something to do with jet/eledb.
It is not possibly for the data to be to large because;
1). I’ve got a string limit function which chops of anything larger that what the field should be and this is far less than the Access DB memo field that most columns are set at.
2). I’ve done a thorough analysis of the data and none if it exceeds the maximum column size.
My vb.net code it fairly typical……
Try
Dim ConnectString, SelectStatement As String
Dim Connect As OleDb.OleDbConnection = New OleDb.OleDbConnection
ConnectString = (My.Settings("Access_db_tests"))
SelectStatement = "INSERT INTO test_information (pk_test_information, department_name)"
Connect = New OleDb.OleDbConnection(ConnectString)
Dim Cmd As New OleDb.OleDbCommand(SelectStatement, Connect)
With Cmd.Parameters
.Add(New OleDb.OleDbParameter("@parameter_pk_test_information", pk_test_information))
.Add(New OleDb.OleDbParameter("@parameter_department_name", department_name))
End With
Connect.Open()
Cmd.ExecuteNonQuery()
Connect.Close()
Connect.Dispose()
Catch Ex As Exception
Dim details As String = "pk_test_information = " & pk_test_information & _
" insert_row_to_Access_database - error message >> " & Ex.Message
log_exception(details)
End Try
Does anyone have any ideas?
Any feedback would be much appreciated.
M
|
|
|
|
|
Martijn Groen wrote: Does anyone have any ideas?
This guy[^] knows almost everything; the first hit is it.
Luc Pattyn
I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages
|
|
|
|
|
The first hit it is NOT! I spent a fair bit of time Googling through this.
Reasoning behind this is
1). the application code runs 100% fine 100% of the time on one user account that has admin privileges but not another admin account that is local (no domain or other policies exist affecting this).
2). The data inputted is not greater than the max size of the Access database column, I have analyzed the data source (every last row and column of every row) and no data is larger than the limit (if the data for a column was too large then the code would not work fine with the exact same data as it did on the first user account)
3). There is a string limiter function that has been tested and it is not possible for the data that gets passed onto this insert code to exceed the limit because it will chop it off at the allowed limit at code level this is actually well below the limit of the columns in the access database.
I just regret this application has to have a sh*tty Access backend. I would have been done and dusted and had the bugs ironed out weeks ago had been on a proper database server backend.
M Access sometimes sux
|
|
|
|
|
Change your OleDbParameter creation code to explicitly define the fields being sent as paramters, such as field type and width. Do not rely on the OldDbParameter class to use its defaults like you're doing now.
|
|
|
|
|
I need a script to upload a file to an FTP server on a daily basis. The code can be in VB Script or Active-X or DOS commands in batch file. I can use window's scheduler to run that script daily. The FTP Server will have user name, pw to upload files.
Please help me in above regard.
Thanks in advance
Srinivas Mateti
|
|
|
|
|
|
Sir i Did nt get u.PLz can u b more clear
Thanks
Srinivas Mateti
|
|
|
|
|
Read the sticky posts on top (The first two posts).
It's not necessary to be so stupid, either, but people manage it. - Christian Graus, 2009 AD
|
|
|
|
|
You made me hover mouse on that link to see if you really searched that code.
It's not necessary to be so stupid, either, but people manage it. - Christian Graus, 2009 AD
|
|
|
|
|
renatcoder ?
Christian Graus
Driven to the arms of OSX by Vista.
Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
|
|
|
|
|
Christian Graus wrote: renatcoder ?
rentacoder for dyslexics
|
|
|
|
|
How to plug/unplug USB serial port problematically?
I am facing some strange issue with my USB serial port.
I want to unplug and plug the USB Serial port Programitically, as i need to refresh the connection between system and hardware connected.Kindly help.......
Thank in advance for the great programmers
|
|
|
|
|
...
It's not necessary to be so stupid, either, but people manage it. - Christian Graus, 2009 AD
|
|
|
|
|
hi you can do this using the registry.
set the DWORD of "Start" in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\{driver}\ to "4" for disable and 3 to enable.
this may help  never tested ^^
|
|
|
|
|
I am looking for some one who did it problematically.
But still thanks for your Solution
|
|
|
|
|
WTF is 'problematically'? I did it while using a problem?
|
|
|
|
|
OP means through code.
It's not necessary to be so stupid, either, but people manage it. - Christian Graus, 2009 AD
|
|
|
|
|
whats the exactly problem you have with usb plugged devices ?
i may can help you out, i wrote a serial component in c# that checks wheather the connection needs to be
closed after unplugging the device and reopend after replug the device to usb without running into exceptions..
|
|
|
|
|
I have connected the usb serial port and started getting the data from the hardware.
Suddenly i will stop the hardware and re run it .Now the problem is when i return the hardware and try to re connect the my application back and try to connect the COM port, it throws me a message the port is already connected and because of this i can not receive the data, kindly help me to understand the stuff
|
|
|
|
|
If you kill the hardware, the classes relating to the serial comms have probably bombed, and your application itself is holding the serial port resource on one of its async threads. I have seen this while programming to a usb/serial device (resol solar controller). When you exit the application the lock is released and then when you start the app again all is fine.
You should check that when you kill the external hardware or pull the connection, the necessary exceptions are being caught and the serial connection is closed gracefully to ensure all resource locks are released.
|
|
|
|
|
The problem is that the stream in the SerialPort class will not be closed if the external hardware will be removed. this is an bug in the framework. to prevent this behaviour the solution is to rewrite a serial port class using unmanaged code or to kill the application like daveauld described above..
serial port communication was not designed to work during the hardware will be removed. in ealy cases this was not possible because the COM was an integrated hardware in the pc not an usb plugalbe device.
i had the same problem and sovled it by rewriting the serial port (internal catching read/write errors and than closing and reopening the filestream on COM).
bless
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
