new_user[ at ]email.msn.com wrote in message ...
[Quoted Text] >hello >Stephen Martinelli wrote in message ... >>Try this link out for connection strings >> >> http://www.connectionstrings.com/>> >>"Albert D.Kallal" <PleaseNOOOsPAMmkallal[ at ]msn.com> wrote in message >>news:u2Sk2K5eGHA.4900[ at ]TK2MSFTNGP02.phx.gbl... >>>> 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, correct. >>> >>> Yes, but if you STILL must be able to open the file direct on that remote >>> server. Remember, a internet connection is about 100 slower then your >LAN, >>> and for the most part, this means that opening a file *OVER* the internet >>> is too slow. Further, you can't use a socket connection to a mdb file. If >>> you LOOK CLOSE at the connection string, note how it ALWAYS resolves to >a >>> full path name. So, that remote server has to be on your LAN, or at the >>> very least, part of your network neighborhood, and you MUST be able to >>> brose freely to that directory where the mdb file exists. >>> >>> You can read the following on using a mdb *over* a WAN as opposed to a >>> LAN....the following is a MUST read if you are using a wan here >>> >>> http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html >>> >>> >>> >>>> 2. No Microsoft Access code elements need to reside on the remote server >>>> except the *.mdb file. >>> >>> Yes, correct. >>> >>>> 3. On the remote server, permissions need be set so that anyone can have >>>> read access to that Access database. >>>> Are these assumptions true ? >>> >>> Yes, in addition, users also need file crate rights, and file delete >>> rights. If these rights are not given, then the appcation will be single >>> user only. (ms-access creates / deletes a temporary locking file in the >>> same directly as the mdb file to handle mult-user collisions - since >there >>> is no "server" to manage this). >>> >>>> >>>> Me.AuthorsTableAdapter.Fill(Me.PubsDataSet.authors)==>Could not find >>>> installable ISAM >>> >>> You don't show what you connection string looks like yet ether. Can you >>> view any data? How did you data bind this??? >>> >>> Check out the examples, or ask in a .net group for the connection string >+ >>> setup. As mentioned, since you don't need, nor are using ms-access, if >>> your server is remote, and you are using a WAN as opposed to a LAN, then >>> sql server express is going to be a much better choice here... >>> >>> >>> -- >>> Albert D. Kallal (Access MVP) >>> Edmonton, Alberta Canada >>> pleaseNOOSpamKallal[ at ]msn.com >>> http://www.members.shaw.ca/AlbertKallal >>> >> >> > >
|