SQL Server 2005 as my BACKEND DATABASE, MSAccess Front-end with fo


J

Jhun Cabas

This is my subject:
"SQL Server 2005 as my BACKEND DATABASE, WHERE ALL MY TABLES AND QUERIES
RESIDES AND MY FRONT-END IS MSACCESS WHERE ALL MY FORMS REPORTS RESIDES etc
etc."

Can I use the ADODB Connection?

This is the scenario:

- Windows 2003 Server with SQL Server 2005 installed on my Laptop
Toshiba (RESIDES THE BACK END DATABASE), then I have a Hub (8 port) LAN
connected them

- Then the other 3 machines (Laptop Toshiba Sattelite Series) AS A
USER (FRONT-END) connected to the modem in the sense that I am going to use
Laptop Toshiba Series as my back end database server, do you think this will
work?

- I am trying to make my PROGRAM as CLIENT-SERVER DATABASE

Question:
1. Do you think this option is advisable? If it is so, then Can I use the
ADDB Connection to access (ADD/EDIT/DELETE) the data over the network?
Instead of ODBC DSN? Well, I am trying to create Client-Server Application in
my small office

Could you please help me? I know that SPLITTING THE DATABASE works fine. But
how about if we use the SQL Server 2005 as SERVER BACK-END DATABASE where all
tables and queries resides and our FORMS, REPORTS, ETC. RESIDES IN MSACCESS.
Do you think this will okay???

please i need your suggestion.....Thanking you in advanced. Jhun Cabas
 
Ad

Advertisements

B

bcap

Typing in all-capitals is considered to be SHOUTING and hence impolite.

Answers in-line below.

Jhun Cabas said:
This is my subject:
"SQL Server 2005 as my BACKEND DATABASE, WHERE ALL MY TABLES AND QUERIES
RESIDES AND MY FRONT-END IS MSACCESS WHERE ALL MY FORMS REPORTS RESIDES
etc
etc."

Can I use the ADODB Connection?

It depends. See below.
This is the scenario:

- Windows 2003 Server with SQL Server 2005 installed on my Laptop
Toshiba (RESIDES THE BACK END DATABASE), then I have a Hub (8 port) LAN
connected them

- Then the other 3 machines (Laptop Toshiba Sattelite Series) AS
A
USER (FRONT-END) connected to the modem in the sense that I am going to
use
Laptop Toshiba Series as my back end database server, do you think this
will
work?

Yes, although you don't mention what operating system you have on the client
computers. And presumably when you said "modem" you meant "hub".
- I am trying to make my PROGRAM as CLIENT-SERVER DATABASE

Question:
1. Do you think this option is advisable? If it is so, then Can I use the
ADDB Connection to access (ADD/EDIT/DELETE) the data over the network?
Instead of ODBC DSN? Well, I am trying to create Client-Server Application
in
my small office

Absolutely it's advisable. Using Access, you have two options:

1. You can use an mdb file (or accdb in Access 2007) as your front-end, with
ODBC linked tables. There's nothing wrong with this, it works OK, and is
most certainly a client-server setup.

2. You can eliminate the ODBC linked tables by using an adp (Access Database
Project) file. This also works OK, although anyone used to "classic" Access
might find it a bit idiosyncratic.

There are technical pros and cons to both routes, and I for one am happy
using either. Arguments each way have been known to rage for weeks. There
is also the thorny question of what Microsoft is going to do with adp's in
future. While Access 2007 was being born, some at MS certainly suggested
that adp's were deprecated and that their recommendation was to use linked
tables. The adp option is still there in Access 2007, but as to whether it
is wise to use it from a future-proofing point-of-view, your guess is as
good as mine.
Could you please help me? I know that SPLITTING THE DATABASE works fine.
But
how about if we use the SQL Server 2005 as SERVER BACK-END DATABASE where
all
tables and queries resides and our FORMS, REPORTS, ETC. RESIDES IN
MSACCESS.
Do you think this will okay???

Yep, go for it.
please i need your suggestion.....Thanking you in advanced. Jhun Cabas

Finally, the local troll, a dolt by the name of Aaron Kempf, is likely to
muscle in on this thread. Ignore anything he says, he is an idiot.
 
J

Jhun Cabas

Well, sorry for the capital letter that i used to be, people really ignored
the capabilities of MSAccess, for me, it's a 95.5 % perfect database, one of
the big company here in the kingdom of Saudi Arabia, they are still using
MSAccess front-end and back end is SQL Server 2000 and works fine, only that
we have to use the MSAccess wisely that's why, before i begin my project, I
am always asking an "EXPERT" that could give an "EXCELLENT ADVISE". One of my
"Client" suggested to use SQL Server 2005 as back-end database and he really
amazed in MSAccess 2007, specially the "menu", which we called them now as
"ribbon". He wants me to use the whole features of MSAccess 2007, frankly
speaking, he buy Windows 2003 Server Enterprise Edition as Operating System
for the Back-end Database. I can not tell "no" and "not to be" for the
reasons that he used to be my old client.

Well, next monday I will install Softwares on Laptop machine, and they are:

Windows 2003 Server Enterprise Edition
SQL Server 2005

Hopefully, that these two softwares will work with me presumably....

Do you have any comments regarding this? Thanks again....
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top