Visual Basic

Wes Aday22-Jul-12 14:38

Wes Aday

22-Jul-12 14:38

Member 4048188 wrote:
tcp\ip chating

So what? You have some other requirement other than using the Internet Protocol for Internet chatting?

Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012

Dave Kreskowiak22-Jul-12 14:43

22-Jul-12 14:43

Member 4048188 wrote:
i get nothing except tcp\ip chating

So how do you epect the messages to get across the Internet?? Carrier Pigeon?

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Wes Aday22-Jul-12 14:49

Wes Aday

22-Jul-12 14:49

Dave Kreskowiak wrote:
Carrier Pigeon

lol... someday I would like to try that smoke signal protocol....

Dave Kreskowiak22-Jul-12 14:55

22-Jul-12 14:55

It predates the Internet and is still used today, so they've got to be doing something right with it!

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Alaa Dael23-Jul-12 15:26

23-Jul-12 15:26

not necessary across the internet , its between users , that users use my application in local lan Example an accounting program in a company any user can send message to other user use the application
i hop the issue is clear now
thanks

Dave Kreskowiak23-Jul-12 16:30

23-Jul-12 16:30

Well, you did say in your original post "I hope I was clear". Nope.

If you mention chat, everyone immediately thinks two remote machines over an IP network.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Alaa Dael24-Jul-12 13:28

24-Jul-12 13:28

yes its not between 2 machines its between users
thanks to you Dave

Dave Kreskowiak24-Jul-12 13:54

24-Jul-12 13:54

That makes no sense. If it's not between machines and is instead between two users, couldn't they just turn their heads and talk to each other??

Of course it's between two machines!

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Alaa Dael25-Jul-12 13:37

25-Jul-12 13:37

Of course it's between two machines
when i mean two user that means two users use same accounting application, and that users one in department of company and other from another department
"again same application on two machines and single DB 'SQL Server"

thanks anyway Dave

Dave Kreskowiak25-Jul-12 14:16

25-Jul-12 14:16

In a world where email is ubiquitous and, almost so, a corporate instant messaging system, is there really a need for this??

I think your application is trying to solve to entirely seperate and unrelated problems that do not need to be in a single application.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

Alaa Dael23-Jul-12 15:38

23-Jul-12 15:38

SQL

not necessary across the internet , its between users , that users use my application in local lan Example an accounting program in a company any user can send message to other user use the application
i hop the issue is clear now
thanks

_obi_1-Aug-12 7:09

_obi_

1-Aug-12 7:09

Dave Kreskowiak wrote:
Carrier Pigeon?

You think that is safe? Roll eyes | :rolleyes:

-obi-

David Mujica23-Jul-12 2:30

David Mujica

23-Jul-12 2:30

This sounds like a homework assignment.

Try something like this ...

Create a message table with timestamp, usernameTo, UserNameFrom, Status (Read/Unread), MessageText.

When someone sends a message, you insert a record into this table.

You would have to create a client application which checks to see if a message is pending for your current user and retrieve it from the db and display it in a chat window.

The other guys who replied are correct, you need to investigate TCP/IP chatting otherwise your client application will be constantly polling the db for new messages. However, i think this basic design will get you through your homework assignment.

Alaa Dael23-Jul-12 15:41

23-Jul-12 15:41

i well try
i think this idea is fine
thanks

vb 6 sql through ODBC

Member 348763221-Jul-12 9:40

Member 3487632

21-Jul-12 9:40

Dim Ssql
Dim dbstatus
Dim rs

'*************

Ssql = " Select * from User_Access A Where A.User_pwd ='1234' "
set rs = Server.CreateObject("ADODB.RecordSet")
rs = DB.execute(Ssql,dbstatus)
Response.Write(dbstatus)
If dbstatus <> 0 Then
'Error code here
Else
'code here
END IF

'*************

The code is working ok . On successful execution of sql statement the dbstatus value is giving -1 . But according to the code it should return 0 for further execution . For other than 0 it will give Error .

I'm executing this on sql server 2005 and in windows 7.

***But the same code On successful execution of sql statement the dbstatus value is giving 0 on some other enviornment where ODBC version and sql server version is different .

Can anyone help me out .
Thanks in advance

Eddy Vluggen21-Jul-12 13:04

Eddy Vluggen

21-Jul-12 13:04

Member 3487632 wrote:
***But the same code On successful execution of sql statement the dbstatus value is giving 0 on some other enviornment where ODBC version and sql server version is different .

You can either change the specs (requirements to run your software), or the software (have it check the version of the available drivers/software and act accordingly). We mostly choose the first option.

Write down the versions of the ODBC-driver, and update the out-of-date systems to match your test-server.

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

Member 348763221-Jul-12 18:18

Member 3487632

21-Jul-12 18:18

Production Environment version :-
OS windows server 2003
sql server 2000
ODBC 3.526.3959.0

My Testing Environment version :-
OS Windows 7
sql server 2005
ODBC 6.1.7600.16385

What shall i change from above to execute the code . Software i can't change i have no authority to do that.Please help me out

Eddy Vluggen21-Jul-12 23:27

Eddy Vluggen

21-Jul-12 23:27

And which of those two returns the correct results?

That's the one with the correct ODBC-version. I suggest you stick to that particular version, and not start supporting "random combinations of versions".

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

Member 348763222-Jul-12 23:14

Member 3487632

22-Jul-12 23:14

Production Environment version :-
OS windows server 2003
sql server 2000
ODBC 3.526.3959.0

My Testing Environment version :-
OS Windows 7
sql server 2005
ODBC 6.1.7600.16385

First one returns the 0
Second one return -1

Passing Property value from Parent to Child

Eddy Vluggen22-Jul-12 23:58

Eddy Vluggen

22-Jul-12 23:58

..and which of those two is correct? The first one with the 0, or the test-environment with the 1?

Write down the version of the ODBC-driver, and make sure the other machine uses the same version.

The reason we "have" versions is because things tend to change. That means that those two ODBC-versions that you are working with work different, with different assumptions. The older one might have bugs that are solved in the new version. The framework might expect the old bug, and not be able to cope with the new version. There's all kinds of stuff that can go wrong, and unless you know WHAT has been changed in the ODBC-driver, you simply use the LATEST version that you tested against.

Bastard Programmer from Hell Suspicious | :suss:

if you can't read my code, try converting it here[^]

SPSandy21-Jul-12 0:38

SPSandy

21-Jul-12 0:38

Hi I am new to VB .Net and is currently using VB2008. I have created a MDI Parent form and and MDI Child Form

On clicking a Menu item in MDI Parent I am trying to Enable/Disable a Text Box in Child. But this is not working. Can somebody tell me how to do this?

In the Menu Iem Click Event I am putting the code as Parent.child.txtbox.enabled = True. But when I run the program the text box is not getting enabled. Frown | :(

Note: The child form is loaded along with the Parent form. It is not called from any menu Item.

Dave Kreskowiak21-Jul-12 3:20

21-Jul-12 3:20

I highly suggest picking up a beginners book on VB.NET and working through it.

Right now, you're just guessing at what may work and that's not a good idea when dealing with the basics of a language and framework.

Your should be declaring an Interface that your MdiChild form implements, exposing a method that the MdiParent form will use to tell the child to enable/disable the textbox.

Public Interface ISampleInterface

    Sub EnableTextBox(enable As Boolean)
 
End Interface
 
 
 
Public Class MyMdiChildForm
    Implements ISampleInterface
 
...
 
    Public Sub EnableTextBox(enable As Boolean) Implements ISampleInterface.EnableTextBox
        MyTextBox.Enabled = enable
    End Sub
End Class
 
 
 
MdiParent code:

    Dim newChild As New MyMdiChildForm
    newChild.Parent = Me
    newChild.Show
.
.
.
    newChild.EnableTextBox = True

If you can't understand this code or have questions on it, you REALLY need to go through a beginner book.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

SPSandy22-Jul-12 1:09

SPSandy

22-Jul-12 1:09

Thanks a lot Dave. I will go through the Beginner's book. But I do have invented a crude method to take care of the same for the time being. Big Grin | :-D

Dave Kreskowiak22-Jul-12 8:15

22-Jul-12 8:15

Don't get into the habit of doing things the wrong way. You're just going to paint yourself into a corner later.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak