error for Import Sybase.Data.AseClient

I am writing a VB .net Windows form application. at the top of one of my Vb.net code pages I have an import statement :

Import Sybase.Data.AseClient

I am getting the following error message though, and I don't have a clue as how to fix it. Can someone help me out? Below is the error message :

Warning 4 Namespace or type specified in the Imports 'Sybase.Data.AseClient' doesn't contain any public member or cannot be found. Make sure the
namespace or the type is defined and and contains at least one public member. Make sure the imported element name doesn't use any aliases.
c:\Users\BobGoldma\Documents\Visual Studio 2010\Projects\BVT\Sybase.Data.AseClient.vb
LVL 2
brgdotnetcontractorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Phil DavidsonCommented:
The error message looks like you are using "imports."  But the statement you show in the post has the word "import."

Does the server that you are running the code have access to the Sybase database?  Namespaces are containers that map a word to an object.  It looks like this mapping is not known to the VB compiler.  The VB compiler doesn't know what Sybase is.  Maybe the VB server doesn't have any Sybase database on it.  Maybe it isn't configured to connect to the Sybase database server.  Maybe a link is broken (e.g., in the network or the sybase server is shut off).

Is there a References folder on the VB server?  There may need to be a reference to the Ase DLL (dynamic link loader).  

Is the imports statement outside of a public class module?

Do you use Project Designer?  If so, can you go to the Reference Page and view the imported namespaces section?

" verify that the containing element is accessible from your project.

    Verify that the containing element exposes at least one Public member."

(taken from https://msdn.microsoft.com/en-us/library/ms234657.aspx)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
brgdotnetcontractorAuthor Commented:
Thank you Phil for the very comprehensive help. I have another VB.net windows forms application on my PC that does access the Sybase server. So I know that all of the working plumbing is in place for Sybase. Because it works with the other application. Let me consider your post and dig into the issue some more.
0
brgdotnetcontractorAuthor Commented:
Thank you Phil. Basically I referenced the Sybase dll file and all is well now. Thanks so much!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.