| Author |
 Topic Search  Topic Options
|
RadioActiveLamb 
Groupie
Joined: 29 December 2005
Location: United States
Status: Offline
Points: 171
|
 Post Options
 Thanks(0)
 Quote  Reply
 Posted: 10 February 2006 at 11:07pm |
Pulling my hair out on this one, and there isn't much hair left... I successfully migrated my Access data to SQL 2000. The forum software is reading the data just fine. when I try to post a new thread/reply or anything else that requires a write, I get this error. I know that someone else had a similar error, but the response wasn't clear. I'm not sure what to do to fix this. I'm using the sa account for authentication to troubleshoot the problem to eliminate any rights problems. Once it works, I'll change the authentication to a more restricted user:
ADODB.Recordset error '800a0cb3'
Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype.
/forum/post_message.asp, line 608
|
 |
RadioActiveLamb
Groupie
Joined: 29 December 2005
Location: United States
Status: Offline
Points: 171
|
Post Options
Thanks(0)
Quote Reply
Posted: 11 February 2006 at 12:19am |
Disregard my issue. Using Borg's procedure, I got it to work. I ran the export directly on the server, so I omitted step 5, and I sent the data to an existing database on the local server. Thanks Borg! I can keep my hair now...
 -boRg- wrote:
- Create the database a blank SQL Server database at your web host
- Run the 'msSQL_server_setup.asp' file to create the database tables, Stored Procedure's etc. on your SQL Server database at your web host
- Use Enterprise Manager to delete ALL the newly created tables on the SQL Server database created at your web host, just leaving the Stored Procedures.
- Now on your local machine open your original Access database in Access
- From the Tools menu in Access, select the 'Upsize Wizard'
- Choose the Upsize option to 'Create a new database'
- Choose 'local as your SQL Server and 'Use Trusted Connection'
- Next select ALL the tables to upsize
- Leave all other options as default
- Once your database tables have been upsized using this method, use the 'Export Tool' in Enterprise Manager to upload the tables to the SQL Server database at your web host which you created the Stored Procedures in earlier
- That should be it
|
|
|
Necronom
Groupie
Joined: 19 October 2001
Location: United States
Status: Offline
Points: 116
|
Post Options
Thanks(0)
Quote Reply
Posted: 11 April 2006 at 5:04pm |
|
I just wanted to put my 2 cents in real quick. I'm currently in the middle of upgradding from Access to SQL, and I'm using the Upsizing Wizard technique as listed above. So far so good. But, for about the last 2 hours I've been going nuts because it kept failing on two of my tables (PMMessages and Authors) and I couldn't figure out why for the life of me. Then I ran Compact and Repair and then tried again, bingo. Everything went smoothly. So if you're doing this, I'd run the Compact/Repair before doing this.
Later!
. necronom .
|
|
|
|
Necronom
Groupie
Joined: 19 October 2001
Location: United States
Status: Offline
Points: 116
|
Post Options
Thanks(0)
Quote Reply
Posted: 11 April 2006 at 6:51pm |
|
Ok... now, I'm at the same point where RadioActiveLamb was. I'm getting the
"Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype." error for the same reasons. The problem is that I used b0rg's method exactly. Arg. RAL: can you tell me what you did for the pick a DSN part when using the upsizing wizard to a current DB? My access db and SQL are on the same server as well.
Thanks!
. necronom .
|
|
|
|
cinemanet
Newbie
Joined: 18 April 2006
Status: Offline
Points: 2
|
Post Options
Thanks(0)
Quote Reply
Posted: 18 April 2006 at 6:09am |
|
Hello, Friends.
I migrate the Access version to SQL Server, but I have some errors:
Microsoft VBScript runtime error '800a005e'
Invalid use of Null: 'CLng'
/forum/forum_posts.asp, line 310
Somebody help!
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 18 April 2006 at 8:50am |
|
It looks like the default value database fields are not being given their default value in your SQL Server database.
Check that all default values are carried across to the SQL Database
|
|
cinemanet
Newbie
Joined: 18 April 2006
Status: Offline
Points: 2
|
Post Options
Thanks(0)
Quote Reply
Posted: 19 April 2006 at 2:29am |
-boRg- wrote:
It looks like the default value database fields are not being given their default value in your SQL Server database.Check that all default values are carried across to the SQL Database
|
The default values are those that are in tblconfiguration and tbldatetimeformat?
In my data base the default values are correctly registered in these tables.
Which are the other tables that are the values standard?
|
|
kingjoop
Newbie
Joined: 01 September 2004
Status: Offline
Points: 11
|
Post Options
Thanks(0)
Quote Reply
Posted: 27 April 2006 at 8:31am |
cinemanet wrote:
Hello, Friends.
I migrate the Access version to SQL Server, but I have some errors:
Microsoft VBScript runtime error '800a005e'
Invalid use of Null: 'CLng'
/forum/forum_posts.asp, line 310
Somebody help! |
Seems like i have the same problem after my access to mql migrate.
|
|
