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
"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