[AccessD] SQL_Svr BE Access FE

Jim Lawrence (AccessD) accessd at shaw.ca
Thu Aug 28 19:44:30 CDT 2003


Hi Stephen:

You could try MySQL as a BE; it free. If you set up your Access FE to use
unbound format then you can centralize everything. You may require a web
server but Windows Apache is also free.

HTH
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Stephen R.
Zayko
Sent: Thursday, August 28, 2003 3:40 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] SQL_Svr BE Access FE


When you say suffer...

My clients do not have the cash for a SQL license at every LAN location.
I tried Access replication once and did a poor job and people hated it.
I do not have much (any) experience with Terminal Server, but that may
be an option for some (but not all) of the users.  Perhaps their IT
staff can help me out with that.

Thanks again everyone for all of you help and input.

Stephen R. Zayko, P.E.

SECOR International Inc.
2321 Club Meridian Drive, Ste E
Okemos, MI 48864

(p) (517) 349-9499 ex24
(f) (517) 349-6863
(m) (517) 204-5136

szayko at secor.com
www.secor.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Haslett,
Andrew
Sent: Tuesday, August 26, 2003 08:03 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] SQL_Svr BE Access FE

Replication.

Unless you have a *very* high speed WAN connection then your performance
will suffer with only a single BE, even with an ADP.  One option is to
replicate the back-end to each office, however this will obviously have
SQL
Server license implications, and therefore $$.  This is one advantage
that
Access has, you can replicate the back-ends without cost!  (Access
replication is a little more flaky than SS though..)

If you do have access to a VPN, then I would encourage users to Terminal
Serve/Remote Desktop to the location where the back-end is located.
This
means the only traffic between offices is the screen 'display'.  No
actual
data would be transferred across offices.

It also saves you having to distribute front-ends to different offices -
you
can just maintain a couple of front ends in the one office - ie. one
front-end for Terminal Server users, and another for each of the users
in
that particular office.  No replication, no distribution of front-ends.
It
*will* mean you probably need a dedicated 'Terminal Server' or at least
a
couple of free machines in that office for users from the other offices
to
Remote Desktop into.

Cheers,
Andrew

-----Original Message-----
From: Stephen R. Zayko [mailto:szayko at secor.com]
Sent: Tuesday, 26 August 2003 10:05 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] SQL_Svr BE Access FE


Thanks Andrew

I am starting from scratch right now.  That was the reason for the first
post:  so that I could start down a path that would have good
performance.  I also wanted to choose the option that would be the most
flexible for me in programming and for the app in future development,
add-ons, and changes.

As for a web based front end... that is out of the question.  Some of
the users have had bad experiences with a WB_FE and will not entertain
the idea.  They like Access, which is good for me!

The clients are employees of a medium sized engineering company.  They
will be accessing the App from each of the ~30 offices throughout the US
and Canada.  Each office will have one FE for an Engineer or Project
Manager to examine status of a job as detailed by input from other
Engineers/Geologists throughout the country.

Is there a fourth way to connect to a BE data source?

-Stephen

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Haslett,
Andrew
Sent: Monday, August 25, 2003 09:36 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] SQL_Svr BE Access FE

If you're starting from scratch then an ADP will offer the best
performance.
You will need to use ADO to interact with the BE which may be a drawback
if
you are used to DAO.

If you already have a front-end then ODBC links may be the best option
as it
will require very little alteration of existing code / queries etc.

You're third option is *basically* what an ADP does, in that it makes
ADO
calls to SQL Server when required.

When you say 'live on the internet' are you talking about your SS BE?
If
so, then perhaps a web-based front end will offer the best solution. Who
are
your clients? Where will they be accessing it from?  Are you
distributing
the FE to numerous locations? etc.

Cheers,
Andrew


-----Original Message-----
From: Stephen R. Zayko [mailto:szayko at secor.com]
Sent: Tuesday, 26 August 2003 10:26 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] SQL_Svr BE Access FE


Dear group:

I was wondering if I could get some input for the following scenario:

I am writing an AccessXP FE for a MS_SQL Server database that will live
on the internet.  I was wondering how would be the best way to connect
to the data (only I can TRULY answer this question)?  But in asking
myself that, I was wondering what the pros and cons of each of these are
and if anyone has strong feelings one way or another on these:

1)  Linked tables via ODBC (using system DSN)
2)  Write the FE as an .adp with tables directly connected to server
tables
3)  Call all connections on the fly to the server where the BE is
located
4)  Some other way that I do not know about.

Most users will have an DSL or T1 connection to the internet.

Thanks in advance for your inputs.

-Stephen Zayko

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

IMPORTANT - PLEASE READ ********************
This email and any files transmitted with it are confidential and may
contain information protected by law from disclosure.
If you have received this message in error, please notify the sender
immediately and delete this email from your system.
No warranty is given that this email or files, if attached to this
email, are free from computer viruses or other defects. They
are provided on the basis the user assumes all responsibility for
loss, damage or consequence resulting directly or indirectly from
their use, whether caused by the negligence of the sender or not.
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

IMPORTANT - PLEASE READ ********************
This email and any files transmitted with it are confidential and may
contain information protected by law from disclosure.
If you have received this message in error, please notify the sender
immediately and delete this email from your system.
No warranty is given that this email or files, if attached to this
email, are free from computer viruses or other defects. They
are provided on the basis the user assumes all responsibility for
loss, damage or consequence resulting directly or indirectly from
their use, whether caused by the negligence of the sender or not.
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list