Out of disk space, MaxLocksPerFile, Memo

Greyowlsl

Mlak Mlak
Local time
Tomorrow, 04:05
Joined
Oct 4, 2006
Messages
206
Hi,

As you can see in the thread heading, i have an issue where i am trying to change a text field into a memo field, but i get the error "There isn't enough disk space or memory", so i changed the MaxLocksPerFile in the registry by following this http://support.microsoft.com/kb/209940
However ive made the maxlocks now 500000000 and it still is giving me the error, im scared to make it any bigger. The table has 71000 records. Do i have to restart the computer for the registry changes to take effect?

Thanks,
Leon
 
Try creating a new Field (Memo) and Appending the Records.

Then delete current Text Field and Finally reName Memo Field.

As a BTW some people place Memo Fields in a Separate Table with a One to One Relationship.

Apparently Memo Field are prone to corruption.
 
it sounds more like a corruption issue. maybe one of the records is corrupt. see if oyu can find it by inspection. thry sorting on the text field. you may or may not be able to fix the corrupt record

one thing you could do is create a new table, and copy and paste the existing data into the new table, ignoring any corrupt records - then fix the corrupt record manually.
 
Pat

I did mean FIELD.

But perhaps I confused the issue by talking about a second table.

Let me try again, but with a different solution.

Create a new Table with Primary Key, Foreign Key and a MEMO field. Join this to the existing Table using the Existing Table's Primary key and the new Table's Foreign Key.

This would then be a One to One Relationship.

Append the Data from the TEXT Field in the existing Table to the MEMO Field in the New Table.

If Successful then delete the Text Field in the original field.
____________________________________________________________

If you have problems then you may have some corruption. In that case post back with the error and we will try to find the corruption.

Hope this makes better sense.
 
Tried your solution RainLover (looked like the least work :P), works great!, no issues at all... yet :P
Thanks to everyone else too.
 
I did forget to say to append the original Primary Key to the new Foreign Key.

I assume you did that.
 

Users who are viewing this thread

Back
Top Bottom