Results 1 to 12 of 12
  1. #1
    4 Star Lounger
    Join Date
    Jan 2001
    Location
    Houston, Texas, USA
    Posts
    432
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Office XP - Problems (OS 2K, Office XP)

    We are using Office XP at our location and we are having problems using Access. No matter how much we complain to the Network Dept. they keep saying at the Managers meetings that everything is working fine and nobody has report any problems. They even say that nobody in other companies are reporting any problems.

    If you are having problems with any of the Office Xp programs could you please forward me a brief message stating what your problems are and if it be fixed. We are looking for ammunition to fight with the Network group and see if we can at least go down to Office 2K.

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Office XP - Problems (OS 2K, Office XP)

    What kind of problems are you having? There certainly are known problems in the initial release of Office XP (and every other version of Office I can recall), hence the service pack that came out almost immediately and all the hotpatches that have followed. Has your IT Dept applied the Jet 4 service packs? It turns out that if you applied SP6 without going through the earlier Jet SPs, you need to download a replication update to patch the patch. <img src=/S/crazy.gif border=0 alt=crazy width=15 height=15>

    Without some direction, you may get lots of complaints about OXP, but it is arguable whether those will help convince your Network Dept without more than anecdotal evidence. For instance, I hate the way Word 2002 messes up numbering when you try to insert it into a document, but that won't persuade anyone you're having problems with Access. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

  3. #3
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    I would add that the problems that I have seen (with the exception of some strange behavior in doing mail merges with Access and Word XP) have all been related to the issue of some workstations running Access 2000 and some running Access XP. I've been using XP for nearly a year now, and in general it is more stable than Access 2000, which in the grand scheme of things behaves pretty well too.
    Wendell

  4. #4
    4 Star Lounger
    Join Date
    Jan 2001
    Location
    Houston, Texas, USA
    Posts
    432
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    We are running into problems all over. The most problems are from Outlook. People complaining that it used to take 3 - 5 seconds to open a message or to create a message. It now takes between 30-40 seconds on average for most of the people. In Word, some of the problems that are being reported is we create a document and save it. At a later date the file is opened and parts are missing, but if you open the same file again at another time it's all there. Some people can only print the upper half of a report and the bottom half is missing. In Access, when requesting for reports 3 out of 10 times it causes access to crash and renames the database. Sometimes after entering 20 records it starts to display the information like bar code lines. Twice it has lost the primary key in the table format. Another dept. has also report loosing the primary key in one of their tables in their database. The shortcut icons have had the path to the database point to different databases.

    We don't use Excel or PowerPoint much so nobody has reported any problems here. Office XP was rolled out in the first week of May, and as more people are being converted the more problems are popping up. The Network Group is not reporting any of this and is passing it on as User errors.

    End of Speech. LOL

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Office XP - Problems (OS 2K, Office XP)

    Well, I run Outlook 2002 on my work machine with no problems. In fact, I don't notice any performance difference between it and Outlook 2k at all. The problems you're describing shriek of network failures, not Office problems. Access is peculiarly sensitive to network failures, regardless of version. I suspect that the OXP rollout coincided with some network tweaking you aren't being told about. <img src=/S/hairout.gif border=0 alt=hairout width=31 height=23>
    Charlotte

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    I agree with Charlotte - this just smacks of network problems. I presume you are using Exchange Server for you Outlook data - we've seen all sort of anomolies when the network starts misbehaving with Outlook to Exchange.
    Wendell

  7. #7
    New Lounger
    Join Date
    Jul 2001
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    I guess I'm looking here to find out if the problems are Office XP or networking.

    So far the biggest problem I've run into are access database that reach 2.095 GB and return an invalid object when I try to compact. The work around was to create a new blank database, import the all the objects into the new db (size of new db is 200 mb). I'm creating a table, and editing additional columns using VB code that was created in Access 95, and been upgraded ever since.

    The other problem is when I copy db results into excel, the cells do not format (just adding commas, and deleting the decimals). So far I have not had to send a pretty formated spreadsheet report out, but that will change sooner or later.

    Any ideas about either will be appreciated

  8. #8
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    Your situation sounds like a general maintenance issue. If you are creating temporary objects at that rate, you may want to go to a Compact On Exit option. The problem is that when a compact is done, you actually have to add a small amount to the existing database, but if it's already max size you can't add anything. If it isn't really growing that fast, then you may want to institute a weekly compact and repair - all databases should probably be done that often anyhow.

    As to exporting data to Excel, if you format it in a query and then export, it should come in cleanly - we do it frequently, and have seen no problems in 97, 2000 or XP. On the other hand, if you mean formating in terms of cell width's, fonts, and number formats, you will need to do that sort of stuff in Excel, or resort to OLE Automation and do the formating as you build the worksheet on the fly.
    Wendell

  9. #9
    New Lounger
    Join Date
    Jul 2001
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    I guess I did not explain very well. This is a database with many linked table, and each linked table is about 800mb. The code that is kicked off builds one table, that is used as a base to build even more tables. The time to build just the first table, append fields, and than populate the appended fields from the linked tables can be 10-20 hours. So it is not a matter of "maintaince". The make table, update queries, and add descriptions based on a field (using VBA) - are eating space in the database, and not releasing it.

    Then when the database reaches maxium size, it will not compact because the "system object does not exist".

    This problem has also been run into with append queries. If the database were really at maxium size, it would not be a problem, BUT when 2 append queries are run, db max size, all objects are imported into an new blank db (because compact no longer works), and the size is decreased by over 1 GB.......

    Please do not tell me that access is not the proper tool for the job being done - that fact has been known for some time - at this time it is the only tool being offered to do the job, and I don't get a choice in the matter.

  10. #10
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Office XP - Problems (OS 2K, Office XP)

    I'm sorry, but this sounds like a very strange database, no matter what engine it's in. Why would you be building tables to build tables to append data from linked tables that are 800Mb in size?

    It definitely *IS* a matter of maintenance because all those append queries and make tables and so forth are bloating the size of the database enormously and none of the space is recovered until you compact. You're also getting the double whammy of subdatasheets, which are turned on by default for new tables, and which can seriously affect the performance of a split database.

    What you're trying to do, for whatever reasons you're doing it, is NOT appropriate for Access, whether you want to hear that or not. It's possible there might be another way to do it that would be appropriate to Access, but this isn't it.
    Charlotte

  11. #11
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    OK - I can see you have a nasty problem. And while Access may not be the best answer (by far), it should be possible to make it work. Since 2 800mb tables would be 1.6GB, 2.5 tables are all that is going to fit in an mdb file. However, the tables shouldn't all have to reside in a single mdb file. It's pretty simple to specify that an append query create a table in a different database, and if you're doing this in code, you can even create that database on the fly, and then simply link to new tables in each of the databases. In that sense, Access databases can be made as large as you want to - within the limit of the number of tables, linked or otherwise, that an mdb file can contain. It might be of value to give us some details on the number of records, table structures, indexing and the source of the data if that can be done without compromizing proprietary info.

    Note however, that if you are really creating tables that are 800mb in size, and you decide you need some indexes on things to improve performance, you may still find yourself bumping against the max database size. As you and Charlotte point out, you are pushing the limits of what Access can do. You would find that SQL Server or Oracle or ..... would do the task a fair bit quicker and with no significant issues. I know of one SQL Server application where they are running queries over 100 TB of data in a distributed DB structure. Talk about orders of magnitude!
    Wendell

  12. #12
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Office XP - Problems (OS 2K, Office XP)

    Can you point me to some of the resources that detail the known issues when going from Office 97 to XP or specifically from Access97 to AXP? I have found some articles in MS Knowledge base but am interested in any other resources.
    Many thanks,
    aap2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •