Hy all,
i have created a database with access 2003 that now experience some slowness problem. i have concluded that is a table that is becomed to big, but i can't delete any record...
it should help me upgrade the database to MSDE? if yes someone could help me?
MAx
This is probably a real common question but I could find the answer. When is it time to start using MSDE for the data? I built a DB that has grown to about 600 mb and expect to reach a gb before I can archive any data. Everything is run fine with the exception of a user conflict once and a while. About 7-10 users.
View 1 Replies View RelatedHello,
I'm considering using another database server (than Access). The application has more and more users so I would like to upgrade the server to a better DBMS in terms of robustness, security and performance.
The client will remain an access application.
I made my short list but it remains open to include another DBMS : MSDE, SQL server, MySQL, Postgres, ...
Do you have any information that could help me to make the best choice, such as :
- benchmark reports
- compare analysis
- case studies
- your opinion
...
My company has finally bitten the bullet and decided to upgrade their systems before their software goes out of date for user support. However, this means that they are about tio upgrade from Office 97 to Office 2003 running on a Windows 2000 operating system.
How much of an issue am I going to face in converting my databases into the new format. I realise there will be DAO/ADO issues but is there going to be anything else? I am acutely aware that I will be having to sort databases out across the whole company nationwide and the fewer surprises, the better.
Has anyone been through this and if so what were the issues?
Regards
Jason
We have added new columns to a table in our developer db. Now we need to get these columns into the client's system.
Their computer is running on Access runtime, so if we change our existing Access db into a Mde would it be possible to upgrade their database with the changes without corrupting any of the client's data? We're quite happy to overwrite the forms, queries etc. but what happens to the client's data? especially when we have made some changes to the database schema e.g added new columns to the table?
We'd be grateful for any help.
I have several clients using the same database structure. If I do any upgrades or mods I currently manually add the new fields to each database. Is there an easier way?
Is there an easy way to upgrade a whole MS Database based on another? Can I either import just the new structure and not duplicate tables; or export and then import to my new blank database with the new structure?
Hi :)
(A2K format, but running on XP, etc)
I have used Microsoft’s Security FAQ and recommendations on this forum and build a split database; secured with one worgroup file for development and one for customers: what is the most appropriate way to upgrade the backend database content (tables mostly) (as the front-end database can just be replaced) at the customers site?
At the customer there is no development workgroup file, so no permissions to change database objects. I would really like to run sql updates from the new FE database. The solution I currently have devised to go around this problem, involves a lot of manual data moving code, to take care of referential integrity etc. However this approach has a higher risk of creating errors and also takes a lot longer time.
Is there something I have misunderstood of the Security FAQ or recommendation on this forum?
Thanx
:)
I have upgraded an Access 2003 application to 2007. However whenever I go to edit the code in 2007 it reprots that the project is locked. I can't find how to unlock it anywhere? Can anyone help please....
Barry
We have been using a shared database (on the server and it's not spilt) that was converted to MDE file and was created in Access 2003, without any issues for more than 5 years now.
Since we upgraded our office to 2010 (and access 2010) all the sudden the autonumber field starts generates a number that is about 40 to 50 records less than what is should generates. All the records for the missing 40 to 50 numbers are still there and we can search them.
The only work around is to run the database and open a new data entry form (at which time the autonumber field will generates a new number) then close the form, and we keep doing that until we reach the number that should be generated next.