Access DB Issues - Again

[Bob Palank]

Remote server hosts a .mdb file but the client cannot access the DB through
VB.Net Express 2005.

My Assumptions:
1. One can use VB.Net Express 2005 to write a client resident application to
access an .mdb file living on a remote server.
2. No Microsoft Access code elements need to reside on the remote server
except the *.mdb file.
3. On the remote server, permissions need be set so that anyone can have
read access to that Access database.
4. The remote server needs to host the .Net Framework 2.0
Are all of these assumptions true ?
What am I missing ?

If the assumptions are true, the local error message

Me.AuthorsTable Adapter.Fill(Me .PubsDataSet.au thors)==>Could not find
installable ISAM does not make sense to me.

TIA for any help.

Bob

[aaron.kempf@gmail.com]

Re: Access DB Issues - Again

mdb is crap upsize it to sql server

duh grow some balls and learn SQL Server; mdb is for jr high kids to
learn databases

[james]

Re: Access DB Issues - Again


"Bob Palank" <bob@stlcc.or g> wrote in message
news:QOocg.1024 $9M5.381@fe02.l ga...[color=blue]
> Remote server hosts a .mdb file but the client cannot access the DB
> through VB.Net Express 2005.
>
> My Assumptions:
> 1. One can use VB.Net Express 2005 to write a client resident application
> to
> access an .mdb file living on a remote server.
> 2. No Microsoft Access code elements need to reside on the remote server
> except the *.mdb file.
> 3. On the remote server, permissions need be set so that anyone can have
> read access to that Access database.
> 4. The remote server needs to host the .Net Framework 2.0
> Are all of these assumptions true ?
> What am I missing ?
>
> If the assumptions are true, the local error message
>
> Me.AuthorsTable Adapter.Fill(Me .PubsDataSet.au thors)==>Could not find
> installable ISAM does not make sense to me.
>
> TIA for any help.
>
> Bob
>
>[/color]

Sure you can. That error can mean a lot of things. Post your code for
connecting to the remote server. That is where some problems occur. If you
haven't checked it out yet, here is a link to ConnectionStrin gs that can
help too:

http://www.connectionstrings.com/

Click on the Access name and then the type of connection and that will get
you started. As I understand it, the Wizards in Visual Basic 2005 Express
Edition, will not connect to a remote server, just the local server on your
machine. But, you can write the connection strings yourself. There is a lot
of good info on using Access remotely. But, in spite of the silly response
you got from another poster, ( actually a childish response) it really would
be better to use SQL Server for a networked database. But, if that is more
than you need, and you don't anticipate heavy usage of your database, then
Access can do the job.
james

[Stimphy]

Re: Access DB Issues - Again

My Assumptions:
1. One can use VB.Net Express 2005 to write a client resident
application to
access an .mdb file living on a remote server.
TRUE
2. No Microsoft Access code elements need to reside on the remote
server
except the *.mdb file.
TRUE
3. On the remote server, permissions need be set so that anyone can
have
read access to that Access database.
TRUE to an extent, you could manage the users through the access
database too.
4. The remote server needs to host the .Net Framework 2.0
FALSE each client needs its own framework installed.
Unless its a web application,.
Are all of these assumptions true ?
What am I missing ?

[Cor Ligthert [MVP]]

Re: Access DB Issues - Again

Bob,

Why don't you use whatever wizard to try.

If it is working for you than the only thing you have to check what is
different with you and the users.

Just as idea

Cor

"Bob Palank" <bob@stlcc.or g> schreef in bericht
news:QOocg.1024 $9M5.381@fe02.l ga...[color=blue]
> Remote server hosts a .mdb file but the client cannot access the DB
> through VB.Net Express 2005.
>
> My Assumptions:
> 1. One can use VB.Net Express 2005 to write a client resident application
> to
> access an .mdb file living on a remote server.
> 2. No Microsoft Access code elements need to reside on the remote server
> except the *.mdb file.
> 3. On the remote server, permissions need be set so that anyone can have
> read access to that Access database.
> 4. The remote server needs to host the .Net Framework 2.0
> Are all of these assumptions true ?
> What am I missing ?
>
> If the assumptions are true, the local error message
>
> Me.AuthorsTable Adapter.Fill(Me .PubsDataSet.au thors)==>Could not find
> installable ISAM does not make sense to me.
>
> TIA for any help.
>
> Bob
>
>[/color]

[Andrew Morton]

Re: Access DB Issues - Again

Bob Palank wrote:[color=blue]
> Remote server hosts a .mdb file but the client cannot access the DB
> through VB.Net Express 2005.[/color]

(I presume you have previous postings on this subject, but I can't see them,
so sorry if you've gone over some of these points before.)

Please define "remote" in this context. Do you mean it's on the same LAN but
in a different room, or...?
[color=blue]
> My Assumptions:
> 1. One can use VB.Net Express 2005 to write a client resident
> application to access an .mdb file living on a remote server.[/color]

AFAIK, it needs access as if it was a file on the local computer - as in
File And Printer Sharing For Windows Networks. Think security holes.
[color=blue]
> 2. No Microsoft Access code elements need to reside on the remote
> server except the *.mdb file.[/color]

Seems reasonable, except I have a suspicion that when it's accessed there
may be other temporary files written.
[color=blue]
> 3. On the remote server, permissions need be set so that anyone can
> have read access to that Access database.[/color]

Full access. To the folder, not just the file.
[color=blue]
> 4. The remote server needs to host the .Net Framework 2.0[/color]

What are you suggesting that has to do with accessing a file?
[color=blue]
> Are all of these assumptions true ?
> What am I missing ?[/color]

Can you access the remote DB file using Access on the client machine? If
not, write an app to reside on the remote machine to provide the interface
to the DB.

Andrew

[Paul Clement]

Re: Access DB Issues - Again

On Mon, 22 May 2006 15:04:01 -0500, "Bob Palank" <bob@stlcc.or g> wrote:

¤ Remote server hosts a .mdb file but the client cannot access the DB through
¤ VB.Net Express 2005.
¤
¤ My Assumptions:
¤ 1. One can use VB.Net Express 2005 to write a client resident application to
¤ access an .mdb file living on a remote server.

Yes, assuming there is some sort of network path available.

¤ 2. No Microsoft Access code elements need to reside on the remote server
¤ except the *.mdb file.

Correct.

¤ 3. On the remote server, permissions need be set so that anyone can have
¤ read access to that Access database.

If the database is being modified then full access is required to the folder where the database
resides in order to create/update/delete the corresponding .LDB file.

¤ 4. The remote server needs to host the .Net Framework 2.0

False. Access is a file based database. The database engine runs on the client.

¤ If the assumptions are true, the local error message
¤
¤ Me.AuthorsTable Adapter.Fill(Me .PubsDataSet.au thors)==>Could not find
¤ installable ISAM does not make sense to me.
¤

Either the Jet database engine components are not correctly installed on the client or your
connection string is invalid. You may want to post some code.


Paul
~~~~
Microsoft MVP (Visual Basic)

[aaron.kempf@gmail.com]

Re: Access DB Issues - Again

i would try user='Admin' password = blank in the connection string.

but more importantly-- sql server express ships with visual basic
express.
why aren't you using it?

mdb is obsolete kid

[Bob Palank]

Re: Access DB Issues - Again

Thanks to all for the ongoing help.
Microsoft Access (.mdb) seems like an excellent database to be used on a server when the file
size is very small and the number of read only hits per day is less than 100. The server cost is
minimal as opposed to the expense of hosting a SQL Server DB.
Another alternative might be SQL Server 2005 Express DataBase.
But first I'd like to get things working with Microsoft Access.

Below is the Connection String from app.config that I'm using along with the error message that results.

=============== =============== =============== =============== =

<add name="CRUD.My.M ySettings.PubsC onnectionString "
connectionStrin g="Provider=Mic rosoft.Jet.OLED B.4.0;
Data Source=some.ser ver.org\ISstude nt\Pubs.mdb;
JetOLEDB:Databa se;
User ID=;
Password=;"
/>
</connectionStrin gs>
=============== =============== =============== =============== =
Me.AuthorsTable Adapter.Fill(Me .PubsDataSet.au thors) has attached to it an
OleDBException was unhandled ===>> Could not find installable ISAM.
=============== =============== =============== =============== ===

Of course, changing the file source to c:\Pubs.mdb works as expected.
This connection string is shown below.
=============== =============== =============== =============== ===========
<connectionStri ngs>
<add name="CRUD.My.M ySettings.PubsC onnectionString "
connectionStrin g="Provider=Mic rosoft.Jet.OLED B.4.0;
Data Source=C:\Pubs. mdb"
/>
</connectionStrin gs>
=============== =============== =============== =============== ============


TIA for all assistance
Bob

[Paul Clement]

Re: Access DB Issues - Again

On Wed, 24 May 2006 09:30:07 -0500, "Bob Palank" <bob@stlcc.or g> wrote:

¤ Thanks to all for the ongoing help.
¤ Microsoft Access (.mdb) seems like an excellent database to be used on a server when the file
¤ size is very small and the number of read only hits per day is less than 100. The server cost is
¤ minimal as opposed to the expense of hosting a SQL Server DB.
¤ Another alternative might be SQL Server 2005 Express DataBase.
¤ But first I'd like to get things working with Microsoft Access.
¤
¤ Below is the Connection String from app.config that I'm using along with the error message that results.
¤
¤ =============== =============== =============== =============== =
¤
¤ <add name="CRUD.My.M ySettings.PubsC onnectionString "
¤ connectionStrin g="Provider=Mic rosoft.Jet.OLED B.4.0;
¤ Data Source=some.ser ver.org\ISstude nt\Pubs.mdb;
¤ JetOLEDB:Databa se;
¤ User ID=;
¤ Password=;"
¤ />
¤ </connectionStrin gs>
¤ =============== =============== =============== =============== =
¤ Me.AuthorsTable Adapter.Fill(Me .PubsDataSet.au thors) has attached to it an
¤ OleDBException was unhandled ===>> Could not find installable ISAM.
¤ =============== =============== =============== =============== ===
¤
¤ Of course, changing the file source to c:\Pubs.mdb works as expected.
¤ This connection string is shown below.
¤ =============== =============== =============== =============== ===========
¤ <connectionStri ngs>
¤ <add name="CRUD.My.M ySettings.PubsC onnectionString "
¤ connectionStrin g="Provider=Mic rosoft.Jet.OLED B.4.0;
¤ Data Source=C:\Pubs. mdb"
¤ />
¤ </connectionStrin gs>
¤ =============== =============== =============== =============== ============

It sounds like your network data source path is invalid. You either have to use a mapped drive
letter or a UNC path. Below is an example which uses a UNC path:

"Provider=Micro soft.Jet.OLEDB. 4.0;Data Source=\\sharen ame\folder\Data base\MyAccessDB .mdb;"

In addition, I'm not sure what " JetOLEDB:Databa se" in your connection string is. This isn't a valid
parameter.


Paul
~~~~
Microsoft MVP (Visual Basic)

[aaron.kempf@gmail.com]

Re: Access DB Issues - Again

RE:

you're full of shit and you've made the wrong conclustion.

Access is a disease; impossible to secure.
and prone to corruption.

are you going to shut down your website every night so you can run a
compact and repair??

MDB is completely worthless; you would be better off using a simple
text file than MDB for a database.




¤ Thanks to all for the ongoing help.
¤ Microsoft Access (.mdb) seems like an excellent database to be used
on a server when the file
¤ size is very small and the number of read only hits per day is less
than 100. The server cost is
¤ minimal as opposed to the expense of hosting a SQL Server DB.
¤ Another alternative might be SQL Server 2005 Express DataBase.
¤ But first I'd like to get things working with Microsoft Access.

[Bob Palank]

Re: Access DB Issues - Again

Here is a thought that might help resolve this issue.
1. Assure that you are able to place a database onto a server that is connected to the internet.
Be sure that the machine you are working on isn't the server.
2. A common DB is of course The Northwind Access database.
3. Using VB.Net Express 2005 drop a Datagrid View onto a form. and set it up so that you can display the CustomerID and Company Name from the Customers Table of the Northwind DB. This can obviously be accomplished without writing a line of code. Run to be sure all is OK.
4. Now create a copy of this Access database in a folder on a server connected to the internet. Preferably a Windows Server such as Windows Server 2003. ( Like www.myserver.com\Test\nwind.mdb )
5. Now examine your app.config file and change the connection string so that it points to www.myserver.com\Test\nwind.mdb
6. Run again to assure all works as expected.
7. If not, then please share what you had to do to get it to run.

I know this sounds sooo simple and I hope it is.
One MCSE said it can't be done!
Others in this thread indicate it can be done.

Thanks for your attention.


"Bob Palank" <bob@stlcc.or g> wrote in message news:S5_cg.1$z_ .0@fe07.lga...
Thanks to all for the ongoing help.
Microsoft Access (.mdb) seems like an excellent database to be used on a server when the file
size is very small and the number of read only hits per day is less than 100. The server cost is
minimal as opposed to the expense of hosting a SQL Server DB.
Another alternative might be SQL Server 2005 Express DataBase.
But first I'd like to get things working with Microsoft Access.

Below is the Connection String from app.config that I'm using along with the error message that results.

=============== =============== =============== =============== =

<add name="CRUD.My.M ySettings.PubsC onnectionString "
connectionStrin g="Provider=Mic rosoft.Jet.OLED B.4.0;
Data Source=some.ser ver.org\ISstude nt\Pubs.mdb;
JetOLEDB:Databa se;
User ID=;
Password=;"
/>
</connectionStrin gs>
=============== =============== =============== =============== =
Me.AuthorsTable Adapter.Fill(Me .PubsDataSet.au thors) has attached to it an
OleDBException was unhandled ===>> Could not find installable ISAM.
=============== =============== =============== =============== ===

Of course, changing the file source to c:\Pubs.mdb works as expected.
This connection string is shown below.
=============== =============== =============== =============== ===========
<connectionStri ngs>
<add name="CRUD.My.M ySettings.PubsC onnectionString "
connectionStrin g="Provider=Mic rosoft.Jet.OLED B.4.0;
Data Source=C:\Pubs. mdb"
/>
</connectionStrin gs>
=============== =============== =============== =============== ============


TIA for all assistance
Bob

[Andrew Morton]

Re: Access DB Issues - Again

Bob Palank wrote:[color=blue]
> I know this sounds sooo simple and I hope it is.
> One MCSE said it can't be done!
> Others in this thread indicate it can be done.[/color]

It is simple if you write a CGI program on the web server to access the DB
file. Not forgetting, of course, to program against SQL injection attacks
[1].

Unless I'm missing something, it is impossible if you try to access the file
directly with http: protocol.

Can you connect to the .mdb-file-on-the-server from Access (the program) on
the client? That is, in effect, what you are attempting.

[1] http://en.wikipedia.org/wiki/SQL_injection

Andrew

[aaron.kempf@gmail.com]

Re: Access DB Issues - Again

yes you can; Data Access Pages do this all the friggin time.

it's the most beautiful feature ever introduced into Access.

especially when you double scoop-- you take the DAP on top of ADP.

DAP friggin rock; ms is a bunch of drunk retards for not being
successful in this market.

-Aaron