|
-
Feb 27th, 2007, 04:28 PM
#1
Thread Starter
New Member
.NEt 2003 not working with Windows Server 2003
Has anyone heard about vb code not working "properly" on Windows Server 2003 operating system?
I have an application that will work as i want it to on different computer all using XP Pro as the ooperating system
Then i tested it on two different Window Server 2003 machines and it works it just doesn't give the result it should and as it does for the XP Pro operating system?
I am wondering if this is a know bug or if there is a fix for either . NET 2003 or for the server operating system.
Thanks
Tricia
-
Feb 27th, 2007, 04:32 PM
#2
Hyperactive Member
Re: .NEt 2003 not working with Windows Server 2003
is this a "networking" type app. i.e. you using sockets or such?
-
Feb 27th, 2007, 05:24 PM
#3
Thread Starter
New Member
Re: .NEt 2003 not working with Windows Server 2003
We are using oracle.client dll for connecting to databases. That is the only "networking" stuff that is in there.
-
Feb 27th, 2007, 05:43 PM
#4
Re: .NEt 2003 not working with Windows Server 2003
How about you explain what you're trying to do and what the different results are? XP and Server 2003 are two different operating systems so of course there will be differences. Perhaps Server 2003 has stricter security in a particular area that you're using so it disallows certain operations. We'd only be guessing though if we don't know what your code does and where the results differ.
-
Feb 27th, 2007, 05:52 PM
#5
Thread Starter
New Member
Re: .NEt 2003 not working with Windows Server 2003
It is hard to explain where the results different as everytime you run the app on server 2003 it gives different result.
One difference is when i am adding and deleting node from a tree
Another was drag and dropping a node into a datagrid (this is where were we take the information from the node and put into the datatables that the datagrid is binded to)
moving row in datagrids (would just replace and thus all the rows would eventually be the same data) We code this functionality as the way it was designed.
Nothing really ever made the program crash at all it just didn't give the results that it was designed for.
I am hoping that it is an issue with VB and not my code (although highly unlikely)
Thanks
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|