| Alex White MCDBA MCSE 2005-05-16, 8:24 pm |
| Hi Karen,
You do not need to split your database, splitting is the process of moving
the data away from everything else in an mdb file, in your situation, you
are using the mdb as a data store only. The fact that your front-end is C++
would normally indicate a pretty good programmer as they have used (In my
opinion) the hardest language to master outside of assembler. I would make
sure you are running the latest MDAC/Jet stuff http://www.microsoft.com/data
make sure your computers are patched and in good working order.
--
Regards
Alex White MCDBA MCSE
http://www.intralan.co.uk
"karen" < nospambugarsnotspam@
ix.netcomspamnot.com> wrote in message
news:Yr5ie.1$x3.68@bcandid.telisphere.com...
>
> "David W. Fenton" <dXXXfenton@bway.net.invalid> wrote in message
> news:Xns9657908503D5
Cdfentonbwaynetinval
i@24.168.128.86...
>
> Ok, I usually lurk, but I have some questions about corruption. I've read
> that the databases should be split, with data on the network, and the
> forms and queries on each individual pc. We use Acess 97, not split, but
> with no queries or forms. All of the user input and queries are done
> through programs written in Visual C++ 6.0. The database lives on the
> network, the programs live on each users' PC. I didn't write the actual
> database code, so I assume it uses JET. It doesn't use ODBC. Most of the
> users have XP, but a few still have Win98, so when I do get a chance to
> make changes in the code, I compile it for both, and have separate
> installs. I do a compact and repair on the databases about once a month,
> when everyone else has gone home. The databases are small: the largest is
> about 30-35MB.
>
> We get corruption, oh, maybe once a year or so. The network is slow
> perhaps, then they start getting error messages. I kick everyone out, and
> see records with #ERROR all across. I've recovered the data by copying
> everything to Excel in the bad database, and then copying it back. (I've
> got to do some funky stuff, since there are autonumber fields to deal with
> as well.) We always lose a few records. Last week we had corruption, and
> the repair wouldn't work, so I restored from backup. I then tried a
> repair from 2002, and it did work (converting the database as well), so I
> managed to give them some of the data they had entered. Some was still
> lost.
>
> So, other than not having enough time to work on this project, and not
> knowing exactly how the database access* works, what am I doing wrong? I
> don't like any corruption, but it still occasionally happens. Do I need a
> split database when the database only has tables? Tell me more about
> transaction logs to rebuild corrupted data stores. (I don't usually have
> physical access to the computer the data resides on, just a network map to
> the drive.)
>
> -k
>
> *access, not Access. Although I certainly don't know exactly how the
> database Access works either!
>
>
|