database unrecognised

[kris]

hello,

I been having an issue with an access database for a quite while now.
To give a brief overview of the problem: I copied a database with 2000 format
onto a computer that has windows 2003 server and access 2007. I have a visual
basic 6 application running on the computer. Occasionally the database
connection string in the vb6 program throws an exception as unrecognised
format. At this point when I try to open the database it asks me to repair
the database. After allowing to go through the repair process everything is
back to normal and working. This issue happened few times in the past couple
of weeks. I looked into trust center, added the path for the database in the
trusted location,tried compacting the database. Is there any issue with the
windows server security? (though I turned off windows firewall) or if there
anything I'm missing during the transition process ? I still use the database
as .mdb. Please do let me know your inputs.

thanks.

 

[Paul Shapiro]

The most common cause of db corruption is network connectivity issues. Allen
Browne has a great discussion at http://allenbrowne.com/tips.html#Corrupt
and suggestions to prevent the problem at
http://allenbrowne.com/ser-25.html.

 

[gllincoln]

Hi Kris,

If this is a multi-user application, you might want to log users in and out,
or automatically track the IP in a log file (append to a log table as soon
as the user opens the VB6 application and append a log off row when the user
gracefully exists the VB6 app.

Corruption usually means bad code or a write is being interrupted
mid-stream. Could be network, but if your network is flaky, you usually
know that from all of the other issues you are seeing. Any chance the server
is getting rebooted or the user forced off while your VB6 application is up
and running?

If you are the only user - this gets a lot easier. Keep a notebook handy,
write down what you did each session, particularly the LAST thing or two you
did before you logged out of the application. You can also create the same
log file for yourself and track your own usage that way - optionally, append
a line to the log file each time you write data to the database. maybe have
a memo field and shove the data being written into the memo field.

Hope this helps,
Gordon

 

[a a r o n . k e m p f]

Paul;

you don't need to blame everything on the network.

the root of the problem is _JET_.

Jet corrupts databases, and it isn't designed to work across LAN, WAN,
Wireless or VPN.

it's just best to upsize to SQL Server and Access Data Projects.

That would save you considerable time, from what it sounds!

-Aaron

 

[Tony Toews [MVP]]

"a a r o n . k e m p f @ g m a i l . c o m" <[email protected]>
wrote:

On Nov 19, 5:11 pm, "Paul Shapiro" <[email protected]>
wrote:

Aaron

See the date Paul wrote that. Do you really think he's going to be
looking for an answer slightly over a month later?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/