August 17, 2009 at 5:09 am
Hi Everyone
I have got bit of a strange issue occuring in one of our access databases.
Background:
-Access database uses SQL Server tables.
-We had access 2000 installed on our client machines which was upgraded to access 2003 at some point.
Problem:
-Once we upgraded to access 2003 from access 2000, access 2003 database started crashing 4 or 5 times a day when user opened specific form.
Investigation:
-I have gone through all the queries which are running when user opens this particular form and i have been able to spot anything unusual.
-One thing i have noticed is the table in sql server has special symbols like "%" in it. Should it be the cause of this issue?
Any help would be much appreciated.
Thanks in advance.
Vivek
Vivek Shukla - MCTS SQL Server 2008
August 18, 2009 at 3:59 am
I would really appreciate any thoughts or ideas guys on this one.
Vivek Shukla - MCTS SQL Server 2008
August 21, 2009 at 12:47 am
1. [Sponsor: Web 2.0 Code Generator - Create robust database and reporting apps from your data! Try it FREE! ] Web 2.0 Code Generator - Create robust database and reporting apps from your data! Try it FREE!
(Sponsor)
2.
[ASP Free News: Distributed Queries in MS Access] Distributed Queries in MS Access
(2006-06-19)
3.
[DevSource News: Using the ASPxScheduler Control from DevExpress] Using the ASPxScheduler Control from DevExpress
(2009-07-15)
4.
[DevSource News: Microsoft Releases SQL Azure Database CTP] Microsoft Releases SQL Azure Database CTP
(2009-08-19)
5.
[ASP Free News: Migrating an MS Access Database to SQL Anywhere with Migration Wizard] Migrating an MS Access Database to SQL Anywhere with Migration Wizard
(2006-03-31)
6.
[ASP Free News: Using Data Access Pages to Access Data on a SQL Anywhere 10 Database] Using Data Access Pages to Access Data on a SQL Anywhere 10 Database
(2006-09-30)
7.
[ASP Free News: Importing Data into MS Access with ODBC] Importing Data into MS Access with ODBC
(2005-10-11)
8.
[ASP Free News: Understanding and Creating an Access Project] Understanding and Creating an Access Project
(2005-10-01)
Migrating from Access 2000 to SQL Server 2000
(Page 1 of 6 )
In this article, we will simulate migrating a relatively small but established business from Microsoft Access 2000 to SQL Server 2000. There are a variety of reasons a business might wish to perform such a migration. Legacy queries, forms, and reports will be taken into consideration, as well as the appropriate way to handle database files.
Growing businesses often come to a stage where they need to migrate their MS Access database to a SQL Server. The reasons for this, apart from the natural growth in the size of the database, are other considerations which may be summarized as follows:
* User base is increasing
* Internet access is increasingly demanded
* Security has suddenly become a issue
* Ready availability is desired.
In such cases, the natural course is to migrate to a SQL Server, maybe via MSDE in the first pass. However, the business has developed a large number of queries, forms, reports, and even placed some of their data for Internet access via DAP. Obviously, it is too much to recreate all this information in the short run. The desirable path would be to retain all those user objects including the queries. You would then export just the tables which can safely stay in the SQL Server, but can be accessed via the network.
In this migration simulation, an access database file, Migrate1.mdb has some five tables, a query, a form, a report and a data access page hosted on the intranet. The tables will be migrated to SQL Server and then linked back to the application. It is shown that user objects on Access are usable and updates to the SQL Server tables are reflected in the access objects. The down side to this is the increase in network traffic.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply