[VB.NET2003] DataControl with MDI

hello,..

Inof: using VB.NET 2003 ADO provider - My Database MS Access2003

i want just simple code of how to add Datacontrol on MDI Parent and control this Datacontrol for each MDIChild?

like if i have these Datacontrol [ Add, Save, Delete, Update, Edit, Print] was installed in MDI Parent with Toolbar and you can by these Datacontrols to control each MDI Child form?

also i have in each MDI Child Form Tabcontrol how to programme this code as you see in my link picture

http://img502.imageshack.us/img502/1...controlsw3.jpg

You will most likely get the help you seek by posting the question to one of the VB.NET Form related forums, or one of the VB.NET or Access related NNTP newsgroups.sql

[ODBC SQL Server Driver]Timeout expired

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied)
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expire
If anyone has any ideas as to possible reasons, it would be immensely appreciated
Any help would be greatly appreciated
Thank you
- A l p e"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:BC471D69-9B62-452C-85BA-2EB1739E686B@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
It is not unusual.
Either your SQL Server get overloaded of quryes, or backup (or other
regulary runned) tasks was too heavy...
Or your query in this page just runs slow.
Or you have a deadlock between your query and another query from task or
another application.
Default timeout I think is 30 seconds. You can change it in connection
object.
Bojidar Alexandrov

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

Our program report the error like this:

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

I used VC++ and ADO.

How does this error happen?

How can I fix it?

Does this can be caused by mutil-thread?

We use the SqlServer 2005.

Thanks

This is caused by you have a opening result set open against the same connection. For example, you execute a SqlCommand to select all rows from a table, while the result set is not drained, you try to execute another SqlCommand using the same connection, you will hit this error message.

To solve this, you have two choices:

a. Make sure you read the rest data from the pending result set before you send the next SqlCommand.

b. Use MARS (Multiple Active ResultSet) connection setting to enable multiple active result set in a connection. See http://msdn2.microsoft.com/en-us/library/ms345109.aspx

for more details.

Thanks!

Ping

|||

Refer to MARS, http://msdn2.microsoft.com/en-us/library/ms345109.aspx.

It is seems that the SQL SERVER 2005 has already fixed it, isn't it?

Thanks

|||

If I'm reading your error message correctly, the issue is that you're using a pre-SQL 2005 driver. Although the SQL 2005 Server understand MARS, you'll need to use the SQL 2005 driver in order for your application to be able to use it.

You'll need to connect using the "SQL Server Native Client" driver instead of the "SQL Server" driver.

Hope this helps!

~Warren

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

Our program report the error like this:

[Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt.

I used VC++ and ADO.

How does this error happen?

How can I fix it?

Does this can be caused by mutil-thread?

We use the SqlServer 2005.

Thanks

This is caused by you have a opening result set open against the same connection. For example, you execute a SqlCommand to select all rows from a table, while the result set is not drained, you try to execute another SqlCommand using the same connection, you will hit this error message.

To solve this, you have two choices:

a. Make sure you read the rest data from the pending result set before you send the next SqlCommand.

b. Use MARS (Multiple Active ResultSet) connection setting to enable multiple active result set in a connection. See http://msdn2.microsoft.com/en-us/library/ms345109.aspx

for more details.

Thanks!

Ping

|||

Refer to MARS, http://msdn2.microsoft.com/en-us/library/ms345109.aspx.

It is seems that the SQL SERVER 2005 has already fixed it, isn't it?

Thanks

|||

If I'm reading your error message correctly, the issue is that you're using a pre-SQL 2005 driver. Although the SQL 2005 Server understand MARS, you'll need to use the SQL 2005 driver in order for your application to be able to use it.

You'll need to connect using the "SQL Server Native Client" driver instead of the "SQL Server" driver.

Hope this helps!

~Warren

[DBNETLIB] 2147467259(80004005) [Connection Write (Send()),] General Network Error

HI all

I am facing a problem on sql server 7 Desktop Engine with front end VB6 and ADO 2.8 my OS is windows 2000 Professional.

ie. I am doing appendchunk to add image files on SQL Table it works fine for Approximately 130 MB, But i am trying to add 249 MB size file it will be showing these error Message.

[DBNETLIB] 2147467259(80004005) [Connection write(send()),] General Network Error check your network documentation.

I do so many way to correct this problem but it stuck up overthere.

In vb appendchunk is completed and the error when Updated command starts (update command also going a long way then show the above mentioned error.

Any body have any idea or clue just tel me for experiment. and complete my project.

Once again I request you please help me.

Thanks in advance.

Note : it is working with Access Database very fine I am tested it But in Access not allow me to store me lots of images its only allow 2 GB storage totally in a table.

Error code 0x80004005 is a generic error that indicates something failed. Either the client or server broke the connection.

Two things you should try:

1. Attach SQL Profiler to trace the execution to determine if it is the client or server that is terminating the connection.

2. Check the ERRORLOG if there are any problems with the server.