Brizar Error

  • Thread starter Thread starter dan.cawthorne
  • Start date Start date
D

dan.cawthorne

Hi Every one,

With in my database, i have 600 Records in one table and my database
is about 30mb in total.

i tried to create a new record through the new project wizard a
created, and when id finished the entry and the wizard exited,

i then decided to go to edit projects form, and for some unknown
reason that last entry i put in, all the text is in Chinese and
Squares,

as any one seen this error before?

Regards

Dan Cawthorne
 
You have most likely corrupted your database. First, always work on a copy
of the database. Working on the original may make it impossible for a repair
service to fix it.

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Try backing up your forms as text with the undocumented SaveAsText
LoadFromText functions:

http://www.datastrat.com/Code/DocDatabase.txt

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

http://www.granite.ab.ca/access/corruptmdbs.htm

for some suggestions. Unfortunately, some corruption cannot be fixed - you
may need to create a new database, import what can be salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com
 
You have most likely corrupted your database. First, always work on a copy
of the database. Working on the original may make it impossible for a repair
service to fix it.

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Try backing up your forms as text with the undocumented SaveAsText
LoadFromText functions:

http://www.datastrat.com/Code/DocDatabase.txt

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

http://www.granite.ab.ca/access/corruptmdbs.htm

for some suggestions. Unfortunately, some corruption cannot be fixed - you
may need to create a new database, import what can be salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com

Thanks for the links and advise, I've alway kept'd a back up of the
database, and I've imported all tables into the back up database,
database seems to work nice and smoothly but ive noticed every time i
shut down the access database i get error and theirs a tick box asking
me to create a back up?

also i think i have some dodgy VB in the database, even though
everything thing works, I've tried to complie the VB but get VB Errors
 
Yes Im Using Access 2003 and i believe it has has been updated to SP3
Applied to Remote Sever thats where I'm running it, Citrix environment

Ive Noticed when ever two people are logged into the same FE and if
one person exits, thats when i get an error and would i like to
restart access and creates a backup? the reason i aint made a FE and
BE cause its seems to run very slow over Citrix, and keeping the
tables and forms in same mcd, seems to be a lot faster?
 
On 7 Oct, 12:53, "(e-mail address removed)" <[email protected]>
Ive Noticed when ever two people are logged into the same FE and if
one person exits, thats when i get an error and would i like to
restart access and creates a backup? the reason i aint made a FE and
BE cause its seems to run very slow over Citrix, and keeping the
tables and forms in same mcd, seems to be a lot faster?

I'm surprised you haven't corrupted yet. Citrix (and terminal server) are
special animals which need special handling. I've built and administered
quite a few Access and SQL-Server databases running on Citrix and Terminal
Server and can tell you that it is very successful if done a specific way:

1. Whenever possible, use a VPN to get to the Server.
2. Certain anti-virus programs (Norton for one) scan the files in and out,
thus slowing down the system.
3. You MUST split the database.
4. Put a copy of the front-end into a folder that only 1 user can access.
5. Do that for each user.
6. NEVER share a front-end

Multiple users sharing a front-end is a recipe for corruption.
 
Back
Top