Nagging question

I created and split my database. I then exported all the tables from the
Warehouse_be.mdb to our SQL Server. I used ODBC Data Source Administrator to
create a new SQL Server data source. Next I linked the front-end to the
tables on the server. The database performs very well.

Here is my question, should I have given the backend MDB to the network
administrators and have them place it on the server (in tact) rather then
exporting the tables to the SQL server? It seems to me the MDB is a container
that not only holds the tables but also has some programming behind the
scenes.


Thanks
Richard

Ps my first post didn’t appear to have gone through, so I apologize if I
double posted.

Richard,

Tables are tables are tables. The only way to get them there is to export
the tables up OR imort them in. I have never heard of another way. You
cannot 'move' the database container to the SQL Server. There is no
programming 'behind' tables, just plain tables holding data.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

"Richard" wrote in message
...
I created and split my database. I then exported all the tables from
the
Warehouse_be.mdb to our SQL Server. I used ODBC Data Source Administrator
to
create a new SQL Server data source. Next I linked the front-end to the
tables on the server. The database performs very well.

Here is my question, should I have given the backend MDB to the network
administrators and have them place it on the server (in tact) rather then
exporting the tables to the SQL server? It seems to me the MDB is a
container
that not only holds the tables but also has some programming behind the
scenes.


Thanks
Richard

Ps my first post didn't appear to have gone through, so I apologize if I
double posted.

On Tue, 6 Jan 2009 20:02:01 -0800, Richard
wrote:

I created and split my database. I then exported all the tables from the
Warehouse_be.mdb to our SQL Server. I used ODBC Data Source Administrator to
create a new SQL Server data source. Next I linked the front-end to the
tables on the server. The database performs very well.

Here is my question, should I have given the backend MDB to the network
administrators and have them place it on the server (in tact) rather then
exporting the tables to the SQL server? It seems to me the MDB is a container
that not only holds the tables but also has some programming behind the
scenes.

A .mdb file can contain code (just as a SQL Server database can contain stored
procedures), but it needn't; in fact the database splitter wizard copies
nothing except tables and indexes into the backend. You're fine having the
data in SQL.

There are some things you can do to make it more efficient, such as basing
your forms on queries that return only one (or a very few) records, but if
it's working ok as is, don't worry about it!
--

John W. Vinson [MVP]

Whew... ty you both for that.


"Gina Whipp" wrote:

Richard,

Tables are tables are tables. The only way to get them there is to export
the tables up OR imort them in. I have never heard of another way. You
cannot 'move' the database container to the SQL Server. There is no
programming 'behind' tables, just plain tables holding data.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

"Richard" wrote in message
...
I created and split my database. I then exported all the tables from
the
Warehouse_be.mdb to our SQL Server. I used ODBC Data Source Administrator
to
create a new SQL Server data source. Next I linked the front-end to the
tables on the server. The database performs very well.

Here is my question, should I have given the backend MDB to the network
administrators and have them place it on the server (in tact) rather then
exporting the tables to the SQL server? It seems to me the MDB is a
container
that not only holds the tables but also has some programming behind the
scenes.


Thanks
Richard

Ps my first post didn't appear to have gone through, so I apologize if I
double posted.

Glad that helped!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II
"Richard" wrote in message
...
Whew... ty you both for that.


"Gina Whipp" wrote:

Richard,

Tables are tables are tables. The only way to get them there is to
export
the tables up OR imort them in. I have never heard of another way. You
cannot 'move' the database container to the SQL Server. There is no
programming 'behind' tables, just plain tables holding data.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" -
Tremors
II

"Richard" wrote in message
...
I created and split my database. I then exported all the tables from
the
Warehouse_be.mdb to our SQL Server. I used ODBC Data Source
Administrator
to
create a new SQL Server data source. Next I linked the front-end to the
tables on the server. The database performs very well.

Here is my question, should I have given the backend MDB to the
network
administrators and have them place it on the server (in tact) rather
then
exporting the tables to the SQL server? It seems to me the MDB is a
container
that not only holds the tables but also has some programming behind the
scenes.


Thanks
Richard

Ps my first post didn't appear to have gone through, so I apologize if
I
double posted.