Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 3 of 3 total |
Error#406 on "REPAIR TABLE" |
Thu, Jan 3 2008 6:42 PM | Permanent Link |
David Michael | I'm getting an Error #406 "invalid table name" when I do a "REPAIR TABLE..."
I think the problem is that the database name is already near the maximum (it's based on a GUID), and the repair process is trying to create a temporary table by concatenating the database name. Which results in a table name that is too long. Is there a workaround for this? Or was it corrected in 1.07 (I'm still using 1.06 right now)? Thanks. -David |
Fri, Jan 4 2008 8:02 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< I'm getting an Error #406 "invalid table name" when I do a "REPAIR TABLE..." I think the problem is that the database name is already near the maximum (it's based on a GUID), and the repair process is trying to create a temporary table by concatenating the database name. Which results in a table name that is too long. Is there a workaround for this? Or was it corrected in 1.07 (I'm still using 1.06 right now)? >> It was corrected in 1.07: http://www.elevatesoft.com/scripts/incident.dll?action=viewaddr&category=edb&release=1.07&type=f&incident=2484 -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Jan 5 2008 3:17 PM | Permanent Link |
David Michael | Great! I'll get the upgrade in place ASAP.
Thanks! -David |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |