Subject | Client Connection Issue Solved! Thanks to ALL who helped me... |
---|---|
Author | delphigurusam |
Post date | 2005-07-28T22:27:27Z |
I was a FB novice when I posted my first plea for help on this issue
back in April. I am barely more than a novice now, having learned
from many people's suggestions. Helen's book was a great resource and
I referred to it often, however, Jason Dodson found my missing link
when he examined my ODBC DSN connection string and observed that I was
using the default OLE provider MSDASQL.1 (as I recall) which MS
defines when adding Firebird DSN's, whereas I should have been using
the ZStyle Ibole.dll OLE provider. Jason helped me install the new
OLE provider and adjust my connection string. A client can now run my
app across a network. Too cool! Aliases are definitely the way to go.
Thanks to all of you and a very special thanks to Jason Dodson.
Sam Hunt
back in April. I am barely more than a novice now, having learned
from many people's suggestions. Helen's book was a great resource and
I referred to it often, however, Jason Dodson found my missing link
when he examined my ODBC DSN connection string and observed that I was
using the default OLE provider MSDASQL.1 (as I recall) which MS
defines when adding Firebird DSN's, whereas I should have been using
the ZStyle Ibole.dll OLE provider. Jason helped me install the new
OLE provider and adjust my connection string. A client can now run my
app across a network. Too cool! Aliases are definitely the way to go.
Thanks to all of you and a very special thanks to Jason Dodson.
Sam Hunt