just a general question

[John]

I am working on a very extensive and complicated application with
A2007. Originally, this app started in 1996 with A1997. It moved to
A2003 and then to A2007 several years ago. It uses SQL Server 2005
for the tables, etc. The db is almost 7gigs in size. The front end,
now A2007, after compacting and repairing is just short of 30mgs (as
an mdb). The front end connects to the sql server with ODBC/DSN
connections. There are a few ADO connection. Before going into
production the mdw is made into a mde file. The compiling process in
the past has given an error about not able to due to some size issue
(or indexes, or something along those lines). To get past it I've
needed to find a form that is no longer used and deleted it along with
the code. Then no more error. Unfortunately, the front end needs to
remain an mdw to mde rather then moving to A2007 extensions. There
are also approximately 100+ people that use the front end. So, this
app is the life blood of the company. I have only been working with
this since may 2008 when I took it over from the person that started
it.

I am wondering if there is a front end size issue that needs to be
kept in mind as the front end continues to update, upgrade, and
evolve? If so, what would it be? Any information would be helpful.

Thanks for reviewing and taking time to respond.
John

 

[Arvin Meyer]

The MDW is the workgroup file for security and must remain undisturbed. You
must be talking about the MDB file as the front-end.

You should have no problems working with hundreds of people with a
SQL-Server back-end.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access
Co-author: "Access Solutions", published by Wiley

 

[John]

The MDW is the workgroup file for security and must remain undisturbed. You
must be talking about the MDB file as the front-end.

You should have no problems working with hundreds of people with a
SQL-Server back-end.
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.accessmvp.comhttp://www.mvps.org/access
Co-author: "Access Solutions", published by Wiley








- Show quoted text -

You are correct, it is mdb file, not mdw.
John

 

[John W. Vinson]

I am working on a very extensive and complicated application with
A2007. Originally, this app started in 1996 with A1997. It moved to
A2003 and then to A2007 several years ago. It uses SQL Server 2005
for the tables, etc. The db is almost 7gigs in size. The front end,
now A2007, after compacting and repairing is just short of 30mgs (as
an mdb). The front end connects to the sql server with ODBC/DSN
connections. There are a few ADO connection. Before going into
production the mdw is made into a mde file. The compiling process in
the past has given an error about not able to due to some size issue
(or indexes, or something along those lines). To get past it I've
needed to find a form that is no longer used and deleted it along with
the code. Then no more error. Unfortunately, the front end needs to
remain an mdw to mde rather then moving to A2007 extensions. There
are also approximately 100+ people that use the front end. So, this
app is the life blood of the company. I have only been working with
this since may 2008 when I took it over from the person that started
it.

I am wondering if there is a front end size issue that needs to be
kept in mind as the front end continues to update, upgrade, and
evolve? If so, what would it be? Any information would be helpful.

Thanks for reviewing and taking time to respond.
John

30MByte is a very modest size for a complex frontend; I've got 100MByte and
larger for some of my apps. If you get an error that you can't resolve, post
the actual error message and someone should be able to help.
--

John W. Vinson [MVP]
Microsoft's replacements for these newsgroups:
http://social.msdn.microsoft.com/Forums/en-US/accessdev/
http://social.answers.microsoft.com/Forums/en-US/addbuz/
and see also http://www.utteraccess.com

 

[Marshall Barton]

I am working on a very extensive and complicated application with
A2007. Originally, this app started in 1996 with A1997. It moved to
A2003 and then to A2007 several years ago. It uses SQL Server 2005
for the tables, etc. The db is almost 7gigs in size. The front end,
now A2007, after compacting and repairing is just short of 30mgs (as
an mdb). The front end connects to the sql server with ODBC/DSN
connections. There are a few ADO connection. Before going into
production the mdw is made into a mde file. The compiling process in
the past has given an error about not able to due to some size issue
(or indexes, or something along those lines). To get past it I've
needed to find a form that is no longer used and deleted it along with
the code. Then no more error. Unfortunately, the front end needs to
remain an mdw to mde rather then moving to A2007 extensions. There
are also approximately 100+ people that use the front end. So, this
app is the life blood of the company. I have only been working with
this since may 2008 when I took it over from the person that started
it.

I am wondering if there is a front end size issue that needs to be
kept in mind as the front end continues to update, upgrade, and
evolve? If so, what would it be? Any information would be helpful.

An mdb file is limited to 2GB so 30MB is just a drop in the
bucket.

Check the error message carefully, it may provide a clue if
some particular resource has reached its limit.

 

[David-W-Fenton]

30MByte is a very modest size for a complex frontend; I've got
100MByte and larger for some of my apps.

!!!!

I'd say 30MBs is a very large front end, unless you're storing
graphics or something in it. I don't have any front ends that are
larger than 10MBs.