A Microsoft Office (Excel, Word) forum. OfficeFrustration

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   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

3011 Jet Database Error Message and others



 
 
Thread Tools Display Modes
  #1  
Old June 6th, 2008, 02:24 AM posted to microsoft.public.access.tablesdbdesign
[email protected]
external usenet poster
 
Posts: 1
Default 3011 Jet Database Error Message and others

I've about run out of things to try so maybe you all can help!

I've got an old Access 97 based VB application that was not well
documented and the programmer is long gone.
This DB is being run on 5 workstations, all running XP Pro SP2.

Due to space issues, I move the database files to a different
volumne. After I move the data 4 of the 5 workstations have had no
problem with accessing the DB. One workstation is having multiple
issues. I ran diags on the NIC (passed), uninstalled and reinstalled
the application, tested the HDD, tested the RAM, compacted and
repaired the database (multiple times) but this one workstation is
getting multiple error messages like:

3011 The Microsoft Jet Database engine coudl not find the object
"Msysdb". Make sure the object exists and that you spell its name and
the path name correctly.

3078 The Microsoft Jet Database engine cannot find the input table or
query 'item'. Make sure it exists and that its name is spelled
correctly.

frmCustomers, DirtyCustomer: Application-defined or object defined
error

3043 Disk or network error

3343 Unrecognized database format 'c:\docume~1\patros~1\locals~1\temp
\jet10e.tmp'.

3075 Syntax error (missing operator) in query expression '4.98+'

I had another machine perform the same tasks (althought I cannot
guarantee the exact same proceedure) on their machine, and had not
problems on two different days.

Does anyone have any ideas?







  #2  
Old June 6th, 2008, 10:52 PM posted to microsoft.public.access.tablesdbdesign
David W. Fenton
external usenet poster
 
Posts: 3,373
Default 3011 Jet Database Error Message and others

wrote in

m:

I've about run out of things to try so maybe you all can help!

I've got an old Access 97 based VB application that was not well
documented and the programmer is long gone.
This DB is being run on 5 workstations, all running XP Pro SP2.

Due to space issues, I move the database files to a different
volumne. After I move the data 4 of the 5 workstations have had
no problem with accessing the DB. One workstation is having
multiple issues. I ran diags on the NIC (passed), uninstalled and
reinstalled the application, tested the HDD, tested the RAM,
compacted and repaired the database (multiple times) but this one
workstation is getting multiple error messages like:

3011 The Microsoft Jet Database engine coudl not find the object
"Msysdb". Make sure the object exists and that you spell its name
and the path name correctly.

3078 The Microsoft Jet Database engine cannot find the input table
or query 'item'. Make sure it exists and that its name is spelled
correctly.

frmCustomers, DirtyCustomer: Application-defined or object
defined error

3043 Disk or network error

3343 Unrecognized database format
'c:\docume~1\patros~1\locals~1\temp \jet10e.tmp'.

3075 Syntax error (missing operator) in query expression '4.98+'

I had another machine perform the same tasks (althought I cannot
guarantee the exact same proceedure) on their machine, and had not
problems on two different days.

Does anyone have any ideas?


If the app is properly designed, it has a back end MDB with data
tables only that's stored on a server, and a front end with
forms/reports/etc. that is stored on each workstation.

Assuming this, then all you have to do is copy one of the working
front ends to the problematic workstation and all problems should be
solved.

If it's not split, then you need to split it. Period. End of
statement. Sharing an MDB, whether unsplit or sharing a front end in
a split app, is simply a bad idea and leads to precisely the kinds
of problems you outline.

If your app is split replacing the corrupted front end should fix
it.

If it's not split, then splitting (and giving each workstation a
copy of the front end) will likely fix all your problems.

--
David W. Fenton
http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
 




Thread Tools
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

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 12:19 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.