BE Storage and Remote Access via FE

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

i am trying to figure how to store BE on an online hosting server and acces
the tables via the FE installed on various computers. i am not familiar with
SQL Server processes, although i do know what it is, and the whole upsizing
scenario makes me nervous due to the required input info that i know not the
answers to. I have read various informative postings on the possible
problems with this type of setup. need clues (or specific instructions) as to
what direction to go.
 
i am trying to figure how to store BE on an online hosting server and acces
the tables via the FE installed on various computers. i am not familiar with
SQL Server processes, although i do know what it is, and the whole upsizing
scenario makes me nervous due to the required input info that i know not the
answers to. I have read various informative postings on the possible
problems with this type of setup. need clues (or specific instructions) as to
what direction to go.
Click to expand...

If you keep the data in an Access/Jet database, then you can't park them on a remote web server and access them from
your desktop. Jet databases don't do remote connections like MySQL or MSSQL. MS used to suggest Remote Data Services
(RDS) for this scenario, but has long since stopped supporting it. Basically, this is a WAN setup, which is NOT
recommended for Access/Jet setups, even if it could be done.

The answer is to move to MySQL or MSSQL for your online stuff, then connect to that database from your desktop. Not sure
if you can do linked tables to a web-based database, but even if you could that wouldn't be advisable.

The other alternative is to convert your desktop app to a full web-based app. This would entail a complete rewrite (yes,
I'm aware of Data Access Pages and such, but they are, at best, lame representations of your application) but will
provide the best performance and such.



Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
 
thx scott,

as to the "move to MySQL or MSSQL" comment: this is what i am lacking info
about. if given specific instructions, i can do this (hint) and have found
several places to put the data. but am still not sure if this is the answer
due to corruption issues i have read about in several articles. one of my
forms has a necessary large recordset and i believe that in order to view or
edit through this form it must all be transfered via the internet to the FE
as the form opens.

my other option could be placing the database files (both FE and BE) on a
server machine in our main office and having users log onto this machine via
Remote Desktop Connection or Terminal Services. i have never used either of
these apps, but could probably figure them out fairly quickly. based on what
i have read, this will allow users to log onto the server machine and do
their updates as though they were sitting at the machine itself, and their
would be no transfer of data over the internet and therefore no corruption
issues due to lost connections, which would be the most likely occurance that
could cause corruption. and this would eliminate the re-write aspect of this,
something i am trying to avoid at all costs.

am i correct in thinking that i cannot safely, or efficiently, access the
..mdb BE remotely via FE on various workstations regardless of whether i place
the file on a server machine in our office, or host it on-line.

pls provide links or info Re: MySQL so i can understand this better. does
the upsizing scenario actually convert the .mdb to something else or do i
have to perform some sort of conversion myself prior to.

thx for any help
 
Scott McDaniel said:
The answer is to move to MySQL or MSSQL for your online stuff, then connect to that database from your desktop. Not sure
if you can do linked tables to a web-based database, but even if you could that wouldn't be advisable.
Click to expand...

Tom Ellison, former Access MVP, once tested an ADP connection from
Access to SQL Server over a simulated 56 kbps dialup line. It was
sluggish but it worked. So security considerations aside using
MySQL/SQL Server on a remote server should work.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Tom Ellison, former Access MVP, once tested an ADP connection from
Access to SQL Server over a simulated 56 kbps dialup line. It was
sluggish but it worked. So security considerations aside using
MySQL/SQL Server on a remote server should work.
Click to expand...

But you have to know what you're doing in terms of designing your
app -- you must be very efficient, even more efficient than you
would be with any server back end on a LAN.
 
i want to thank everone who responded to my questions. (sorry it took two
years to do so)
i've learned a lot since then, mostly from this forum.......

as to the application mentioned in this post, i did actually complete the
project, terminal server sessions was the solution. worked great and exactly
as needed. i could not have done it without all the info from you all.

i am now back with new project, (mySQL this time) with new questions. (my
old post came up in the search......)

i will begin a new thread, hope to hear from everyone who was so helpful
before.
 
Back
Top