So what's the secret??

[rizd999]

For a couple of years, I've had a standard Access 97 split database over a network where the backend was on a server and the interface was installed on each client machine. Performance has never been an issue with this setup regardless of data travelling over the LAN and running it on P2-350s.

As time went on, we've been upgrading systems to better P4s and newer Office2k, Office XP and recently Office2k3 suites and I've been just patching our database system to work with these newer releases at the price of performance. Recently, I've decided to see what I can do to help performance on these newer systems (as the older ones are on the minority now) and so I backed up the original backend and converted to a new 2002 version. And after that, I went ahead ran the new security wizard to create a new workgroup security file, also modified the SubDatasheet Name to None as Microsoft suggested, compacting it a dozen times, etc. and I still can't run this thing with decent performance!! And this is not because of my forms/coding/queries right now as all I'm trying to do is bring up a linked table and this will take a WHILE before it displays.

For example, after I login to my 2002 converted (interface and backend) database and double-click on one of the linked tables, I have time to walk over to the older P2-350 running Office97, login to the original database (that is still on the network server), double-click on the linked table (which only takes 2-3 seconds to display, walk back to my desk sporting the uber-system, sit down and still wait an additional 20 seconds before that similar linked table is displayed!! Other than the conversion, both databases have the same data, are on the same server and are both locked from any user. I don't get it..... Is there something I missed??

Is there anybody out there that would care to offer me any insight on how to get Access XP to perform as well as Access 97 over a network?? TIA!!

 

[rizd999]

What, is everyone experiencing the same thing?? Are there no recommendations or blatant things that I'm doing wrong??

 

[Royal Presence]

Undecided

Hi,

I understand your dilemna. I am only a semi-architect at best, but we hired a consultant to actually determine the best method to present our db to the company. We were assured there would be no problems with our server. We were presented with options of doing both. I opted to go the stand alone, no split issue. I actually have the consutlant telling me now to split it. I can't make myself do it. I am paralyzed. I've heard these scenarios over and over again. I don't know the best answe
r. I don't understand Microsoft with their new versions, etc. I am a Microsoft Baby, but in the last two years, I'm so discouraged with them, I'm very frustrated.

Let me know how you transpire. I admit, it's exasperating at best.

I go into work each day, saying 'no'. I feel very alone for sure. I thought hiring the consultant would help, but they are pressuring me. Things work fine now, no crashes. All we have our development issues and user training facing us. We are working with 2002 Windows XP. The only real obstacle we face is machines not up with 2002, so cannot view our files. We upgraded so most of us could work with it. Do let me know what other feedback you are getting or your opinion. I feel like I'm in a divided camp.

Thanks

 

[Oy Vey]

You can try a few things here, although the changes, if they do work will need to be set on each machine.

1. Tools | Options | General tab : Turn off all Autocorrect features

2. Start a new access database that does not use your workgroup security model. Place the backend in the same location as the production database and try to link to it.

3. Create a new Access database file (again, no security) and import the objects from your current back-end database. Link to it, see if the problem persists.

4. Apply your security to the new database, test again.

 

[rizd999]

You can try a few things here, although the changes, if they do work will need to be set on each machine.

1. Tools | Options | General tab : Turn off all Autocorrect features

2. Start a new access database that does not use your workgroup security model. Place the backend in the same location as the production database and try to link to it.

3. Create a new Access database file (again, no security) and import the objects from your current back-end database. Link to it, see if the problem persists.

4. Apply your security to the new database, test again.

I already had tried your first suggestion also but your other suggestions seem like good ideas on troubleshooting the issue.
It wouldn't be too bad if I had to install the newer settings on each client machine as I had already implemented this cool little feature that upgrades itself when it finds something newer on the server. The only real issue right now is trying to find the reason for the performance degradation with an Access 2002 DBS converted from 97. Anyway, I'll go ahead and try your suggestions. Thanks!!


Royal Presence,

So I take it that you already converted your DBS from 97 to 2002 or is this a new DBS application that you just created in 2002? How many users are going to access this database? at one time? Splitting the database is one issue (and does have its advantages in a site with more than 5 people accessing it) and upgrading to the new version is another issue. Unfortunately, the latter is unavoidable. We can't just order new systems and keep an older version of Office on it just so that it is compatible with our current software. As software implementers, we should adapt but damn....you'd think that Microsoft would make it easier on us. Anyway, I'll keep you updated on what results I get from Oy Vey's suggestions.

 

[The Stoat]

Hi,

Again i can't offer a solution but in the quest to find the problem this may give some answers.

On the server

(1). Create a new db with a brand new table in 2002. Stick a field in it and import some data from Excel I suggest 65000 rows of 10 digit numbers.

(2). Do the same in a new 97db and convert the 97db to 2002.

Create another blank 2002 db on a workstation and link to the new backend table (1) and the converted back end table (2).

Test to see if there is any opening time difference.

This does sound like Oy Vey's method i admit but it will give you a direct comparison of the two processes on identical information without relying on any previous conversion alterations etc.

If the two tables can be opened at the same speed then you will know that the problem lies specifically with your database or an object within it.

There may be an object that is corrupted/bloated and is causing problems.

Little comfort i know but it may help. Good luck.

The Stoat