Subject | Re: [IBO] [OT] IBO / Firebird1.5 can't work with remote DB |
---|---|
Author | Andreas Bednarek |
Post date | 2003-10-23T13:06:01Z |
Hello,
yes I know that WSAStartup is a Winsock function, but I thought my self the
problem could be caused by IBObjects somehow (or my application settings of
course), because various tools like IBExpert don't show any issues with such
remote connection.
Now I corrected that mistake with classic server and am running superserver.
The problem si still there.
I hope this is not that much off-topic, I still believe it is caused by and
related to IBObjects somehow...?
Regards,
Andreas
yes I know that WSAStartup is a Winsock function, but I thought my self the
problem could be caused by IBObjects somehow (or my application settings of
course), because various tools like IBExpert don't show any issues with such
remote connection.
Now I corrected that mistake with classic server and am running superserver.
The problem si still there.
I hope this is not that much off-topic, I still believe it is caused by and
related to IBObjects somehow...?
Regards,
Andreas
----- Original Message -----
From: Daniel Rail
To: IBObjects@yahoogroups.com
Sent: Thursday, October 23, 2003 2:30 PM
Subject: Re: [IBO] [OT] IBO / Firebird1.5 can't work with remote DB
Hi,
This is slightly off-topic for this group.
At October 23, 2003, 08:43, abedna2000 wrote:
> Then trying to open another table 'UNITS' I get this message
> immediately on IBOTable.Open.
> ISC ERROR CODE:335544721
> ISC ERROR MESSAGE: Unable to complete network request to
> host "andris".
> Error writing data to the connection.
> Application didn't call WSAStartup, or WSAStartup was not succesfull.
> STATEMENT: TIBOInternalDataset: "<TApplication>
> (I translated a piece from Czech language, hope it's ok).
This error is not related to IBO, but to Winsocks. WSAStartup is a
Winsock function that the application uses to tell which Windows
Sockets version it is going to use. So, in this case, the error is
probably coming from fbclient.dll. I've never seen the error, nor has
it been reported by my clients, as of today.
As I can see, you are running Firebird 1.5 classic, could you try with
Superserver to see if the problem persists?
If you possible, could you post the answer on the firebird-support
group on Yahoo Groups!
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.