MSDE

  • Thread starter Thread starter Michael S. Montoya
  • Start date Start date
M

Michael S. Montoya

I have on several occasions created databases that ran quickly. But once I
split the tables out into another MDB database and link to those tables, I
notice the front end takes ALOT longer to load and process. I even try
copying the front end to everyone's local hard drive but that doesn't seem
to help any.

I had heard once of using MSDE (my client's projects are not yet "worthy" of
purchasing SQL server). Where can I get more information on how to use
Access with MSDE?
 
I would always make my users run local copies. It protects the original
copy, & should give better performance.

When you connect to SQL Server authentication will occur, this could explain
the time difference in loading. In all honesty, I expect SQL Server would be
slower than a small mdb (with small numbers of records etc) file used by
individual users. However it will give the same performance for n users,
where Access will not...
 
I am not using SQL currently. I am experiencing the delay using the Access
Front end AND back end.

I was wondering about MSDE and how to use it with Access
 
This is taking longer because more data must now travel on the network.

With MSDE, if you don't know what you are doing, it will probably even take
longer than with using Access as the BE. You have essentially 4 choices:

1- Use linked tables to MSDE (or SQL-Server, no practical difference in
your case) : this is without doubt the must easier solution but also the
must slower. You can probably achieve it in less than a few hours.

2- Use linked tables to MSDE but take the precaution of creating a lot
of views to minimize the network traffic, especially in case of joined
tables. You will get a much better performance and lower network traffic
but it requires that you know exactly what you are doing.

You can also add here and there some stored procedures and accessing
them using SQL Passthrough.

This big avantage of this one is that you can build it using the
first solution as your starting point but forget about achieving in only a
few hours.

3- Use an ADP project instead and a lot of Stored Procedure - very high
performance, very low network traffic but a much, much harder solution for
newbies and at leat one month of development for someone who knows what to
do.

4- Forget now about Access and go directly to the .NET Framework: this
solution have a very step learning curve but is the way of the future,
without any doubt in my mind (but you will probably find a lot of people
telling you exactly the reverse).

S. L.
 
-----Original Message-----
I have on several occasions created databases that ran quickly. But once I
split the tables out into another MDB database and link to those tables, I
notice the front end takes ALOT longer to load and process. I even try
copying the front end to everyone's local hard drive but that doesn't seem
to help any.

I had heard once of using MSDE (my client's projects are not yet "worthy" of
purchasing SQL server). Where can I get more information on how to use
Access with MSDE?


.no comen
Click to expand...
 
-----Original Message-----
I have on several occasions created databases that ran quickly. But once I
split the tables out into another MDB database and link to those tables, I
notice the front end takes ALOT longer to load and process. I even try
copying the front end to everyone's local hard drive but that doesn't seem
to help any.

I had heard once of using MSDE (my client's projects are not yet "worthy" of
purchasing SQL server). Where can I get more information on how to use
Access with MSDE?


.
I don't know
Click to expand...
 
Back
Top