FE/BE question

[asawyer]

If I'm creating a A2003 application that will only use SQL Server has the BE
Database, do I really need a FE/BE arrangement for the .mde files?
I would expect all the data to be in sql server, so even small tables that I
would copy to the local machine for performance would still be in sql
server.

Am I missing something or does that make sense?

Thanks,
Alan Sawyer

 

[John Vinson]

If I'm creating a A2003 application that will only use SQL Server has the BE
Database, do I really need a FE/BE arrangement for the .mde files?
I would expect all the data to be in sql server, so even small tables that I
would copy to the local machine for performance would still be in sql
server.

Am I missing something or does that make sense?

Thanks,
Alan Sawyer

If your tables are in SQL, then the SQL database is *by its very
nature* the backend. Your Access database will not have any tables at
all, only links to the SQL tables: i.e. it will be just a frontend.

You don't need to use the database splitter wizard - because you don't
have any local tables to start with!

John W. Vinson[MVP]

 

[asawyer]

That's what I was thinking but I wanted to make sure.
I will have some local temporary tables in the FE database, but that's about
it.
Thanks,
Alan

 

[Albert D.Kallal]

That's what I was thinking but I wanted to make sure.
I will have some local temporary tables in the FE database, but that's
about
it.
Thanks,
Alan

You still have to place the FE on EACH workstation to make this work
correctly.....

If there is any doubt as to why you need to do this, you can read the
following article:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[asawyer]

Yes, I do understand.
Now will something like Auto FE Updater work, or should I create something
myself??
Alan

 

[Larry Linson]

I will have some local temporary
tables in the FE database, but that's
about it.

You will save yourself some trouble, if you look at the example at MVP Tony
Toews' site, http://www.granite.ab.ca/accsmstr.htm, and create your
temporary tables in a temporary database. Then when you are through with the
temporary tables, KILL the temporary database. That will save you having to
compact your front-end with such frequency.

The only tables that are appropriate for inclusion in the front-end are
control tables (e.g., version information) and local lookup tables (e.g., US
states and Canadian Province with their abbreviations, or Departments of the
Company, or ...).

Larry Linson
Microsoft Access MVP

 

[Albert D.Kallal]

Yes, the autofe will work just fine.

I wrote my own, and I shell out to another file (upgrade.mde) that copies
the new FE.

So, roll your own, or use Tony's? Hum, I don't know, I suppose if you don't
have anything...I would grab Tony's...

I wrote my own in a "real" hurry a few years ago...real simple...but I still
use it today....

 

[asawyer]

I know Tony's does a lot, but simple may work here.
You don't happen to have yours on your website or anything do you?
Alan