If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > PC based Database Applications > Brilliant Database > Brilliant Database - Too Large String ERROR

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old
Registered User
 
Join Date: Nov 2012
Posts: 20
Brilliant Database - Too Large String ERROR

Hi - I've been using BD Ultimate for some time with no problems, however, one of my database used in a business situation has an error message of "Too Large String: 12234455 etc".
The database will not open at all and Brilliant Database can only be be closed via the task manager.

Any ideas how this can be put right or how I can get into the file?

Many thanks
Paul
Reply With Quote
  #2 (permalink)  
Old
Registered User
 
Join Date: Jul 2012
Location: Ireland
Posts: 578
If you cannot open the database at all, I'm afraid there is nothing you can really do to repair it then. It's most important to be at lease be able to open it to run the maintenance repair on it.

All I can say is that I hope you implemented a backup system within the database itself or the normal server backups are an option for you to revert to.

If you didn't have you really need this restored, you could consider sending it back to brilliant database. They will for a charge repair it. Providing you can get them to answer your email.

Regards
James
Reply With Quote
  #3 (permalink)  
Old
Registered User
 
Join Date: Jul 2012
Location: Ireland
Posts: 578
Me again.....
Are you 100% sure you don't have your database set to create a backup of itself when opened ?

If you do, and it crashed, there will be perfectly working copy of it in the same path where you where running the database from. It will have a ~1 on the end of it or some other number depending on how many times it crashed.

Beyond that, I cannot think of anything other than going to the server backup. Surly there's one there.
Reply With Quote
  #4 (permalink)  
Old
Registered User
 
Join Date: Jul 2011
Posts: 130
Quote:
Originally Posted by Tubbritt View Post
Me again.....
Are you 100% sure you don't have your database set to create a backup of itself when opened ?

If you do, and it crashed, there will be perfectly working copy of it in the same path where you where running the database from. It will have a ~1 on the end of it or some other number depending on how many times it crashed.

Beyond that, I cannot think of anything other than going to the server backup. Surly there's one there.

I used to have this type of problem earlier. When I analysed it has happened when you store more number of attachments in the database records.Also when synchronize two database by forms and queries particularly the relational one. If the database you are importing is clean and simple you do not get issues.
Eventhough the error comes keep pressing the enter button sometimes it opens with some limitations but that is enough to repair the database or bring your valuable records.
Also when you design a database follow a correct convention in naming forms and vaiables.
Be sure atleast once in a week optimize the database.
Reply With Quote
  #5 (permalink)  
Old
Registered User
 
Join Date: Sep 2013
Posts: 15
Post Convention for name of forms and variables

Where can I get correct convention for naming forms and variables? Is there convention mentioned in brilliant database help?
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On