By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,040 Members | 1,815 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,040 IT Pros & Developers. It's quick & easy.

Connecting backend and frontend

P: n/a
I am trying to connect my backend whih is stored on a public server as
accdb file. This connects well on a local network but when I store the
BE on my ISPs server I get following error in Access 07 "Not a valid
file name"

Can anyone tell me what is wrong with this configuration?

matuag
Access 2007
Win XP
Jul 24 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Actually it's hard to think of anything that's *right* with this
configuration!

Re your specific problem with the file name, how are you referring to the
file? The file name is gonna have to be fully qualified with the server
name or IP address, unless you can map the drive.

More generally, splitting an Access front-end/back-end across the internet
will give you (i) hopeless performance and (ii) frequent corruptions of the
back-end.

If you really need to do this, then you should use a server database engine
(e.g. SQL Server) as the back-end.

"Matuag" <ma****@gmail.comwrote in message
news:19**********************************@m3g2000h sc.googlegroups.com...
>I am trying to connect my backend whih is stored on a public server as
accdb file. This connects well on a local network but when I store the
BE on my ISPs server I get following error in Access 07 "Not a valid
file name"

Can anyone tell me what is wrong with this configuration?

matuag
Access 2007
Win XP

Jul 24 '08 #2

P: n/a

"bcap" <bc**@nospam.nowherewrote in message
news:48**********************@news.zen.co.uk...
Actually it's hard to think of anything that's *right* with this
configuration!

Re your specific problem with the file name, how are you referring to the
file? The file name is gonna have to be fully qualified with the server
name or IP address, unless you can map the drive.

More generally, splitting an Access front-end/back-end across the internet
will give you (i) hopeless performance and (ii) frequent corruptions of
the back-end.

If you really need to do this, then you should use a server database
engine (e.g. SQL Server) as the back-end.
And, then find a server provider who supports your database on their SQL
Server, and negotiate a price.

Larry Linson
Microsoft Office Access MVP
Jul 29 '08 #3

P: n/a
Connect the back end, as in linked tables? Can't link to tables in an accdb
file with the http protocol within Access. You can connect using a
connection string with the ADO or DAO libraries in a VBA procedure.

Chris
Microsoft MVP
Matuag wrote:
>I am trying to connect my backend whih is stored on a public server as
accdb file. This connects well on a local network but when I store the
BE on my ISPs server I get following error in Access 07 "Not a valid
file name"

Can anyone tell me what is wrong with this configuration?

matuag
Access 2007
Win XP
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200807/1

Jul 29 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.