Hello, all.
So we're all happy with Access. Or Access is "good enough" with most
of our applications. I built a split database here at work that has
about seven users who are on pretty much the entire workday. The
backend is on the server with each client having a frontend.
I've spent the past couple days researching corruption because I am
constantly restoring backed up copies of my backend. Usually once a
week I have to restore a backup or create a new database and import
all the objects from the old database. This is getting to be a pain
because the database is a growing 500mb and making my coworkers pissed
off. Thank God that I have a redundant error logs (sometimes the
error log become corrupt!) to record when the backend is broke. I am
confident in my backend design and client VB code (over three years
experience writing/designing) but some tables in the database just
become corrupt by not allowing record additions. I'll try to add a
record myself, one that I know is unique, but still Access gives a
message that an existing record already exists in the table. From
reading corruption articles from this newsgroup and the Microsoft
website I've noticed that a lot of the corruption issues have to do
with hardware and networking equipment such as: faulty NIC's,
hibernation of client's PC's, intermittent network connections.
So my question to all of you is the following: is the solution ASP?
Is the solution to use Access as a backend and use browser forms to
interact with the database? I've built three HTML and ASP websites
with Access as the backend and have never had any problems. Let me
reiterate, no problems at all. There would probably be performance
issues with over ten or so users but with less than ten users I think
it would be the way to go.
I would appreciate people's thoughts on the matter.
Fred
7  1937 
I have notice this kind of thing with my customer's database. It is
VB6-ADO I suspect: I didn't write it, its secured and I don't want to
mess with it - they purchased it from another vendor). But it is over
400 Mb and it got corrupted several times (not nearly as frequently as
yours though - like once in 3-4 months). I keep daily backups of it so
it has not been that much of a pain.
Is BE properly repaired/compacted? It is becoming rather large. Maybe
its time to upscale.
Pavel
Fred MacMurray wrote:
because the database is a growing 500mb
fm********@juno.com (Fred MacMurray) wrote: I've spent the past couple days researching corruption because I am
constantly restoring backed up copies of my backend. Usually once a
week I have to restore a backup or create a new database and import
all the objects from the old database. This is getting to be a pain
because the database is a growing 500mb and making my coworkers pissed
off. Thank God that I have a redundant error logs (sometimes the
error log become corrupt!) to record when the backend is broke. I am
confident in my backend design and client VB code (over three years
experience writing/designing) but some tables in the database just
become corrupt by not allowing record additions. I'll try to add a
record myself, one that I know is unique, but still Access gives a
message that an existing record already exists in the table.
You sound fairly knowledgable so my commment is something you may already be aware
of. Are there unique indexes present on fields which aren't the primary index which
are causing the record additions to not be allowed?
From
reading corruption articles from this newsgroup and the Microsoft
website I've noticed that a lot of the corruption issues have to do
with hardware and networking equipment such as: faulty NIC's,
hibernation of client's PC's, intermittent network connections.
Not at all. The most common problem is the OpLocks problem which is especially
apparent when an app is converted to Access 2000 or newer or when the first Win 2000
client is added to a network consisting of a Win NT/2000/2003 server and until now
Win 95/98/ME clients.
Other problems can be caused by differing SR or Jet versions on clients. See the
Access Corruptions FAQ at my website.
So my question to all of you is the following: is the solution ASP?
Is the solution to use Access as a backend and use browser forms to
interact with the database? I've built three HTML and ASP websites
with Access as the backend and have never had any problems. Let me
reiterate, no problems at all. There would probably be performance
issues with over ten or so users but with less than ten users I think
it would be the way to go.
I don't think so because you lose the rich event model of Access, subforms and combo
boxes become uglier, and it's likely a lot more work.
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 Toews" <tt****@telusplanet.net> wrote in message
news:ma********************************@4ax.com... fm********@juno.com (Fred MacMurray) wrote:
I've spent the past couple days researching corruption because I am
constantly restoring backed up copies of my backend. Usually once a
week I have to restore a backup or create a new database and import
all the objects from the old database. This is getting to be a pain
because the database is a growing 500mb and making my coworkers pissed
off. Thank God that I have a redundant error logs (sometimes the
error log become corrupt!) to record when the backend is broke. I am
confident in my backend design and client VB code (over three years
experience writing/designing) but some tables in the database just
become corrupt by not allowing record additions. I'll try to add a
record myself, one that I know is unique, but still Access gives a
message that an existing record already exists in the table.
You sound fairly knowledgable so my commment is something you may already
be aware of. Are there unique indexes present on fields which aren't the primary
index which are causing the record additions to not be allowed?
From
reading corruption articles from this newsgroup and the Microsoft
website I've noticed that a lot of the corruption issues have to do
with hardware and networking equipment such as: faulty NIC's,
hibernation of client's PC's, intermittent network connections.
Not at all. The most common problem is the OpLocks problem which is
especially apparent when an app is converted to Access 2000 or newer or when the
first Win 2000 client is added to a network consisting of a Win NT/2000/2003 server and
until now Win 95/98/ME clients.
Other problems can be caused by differing SR or Jet versions on clients.
See the Access Corruptions FAQ at my website.
So my question to all of you is the following: is the solution ASP?
Is the solution to use Access as a backend and use browser forms to
interact with the database? I've built three HTML and ASP websites
with Access as the backend and have never had any problems. Let me
reiterate, no problems at all. There would probably be performance
issues with over ten or so users but with less than ten users I think
it would be the way to go.
I don't think so because you lose the rich event model of Access, subforms
and combo boxes become uglier, and it's likely a lot more work.
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:
Have you ever visited the MVP site? http://mvp.org
Dean Arnold, MVP
Tony,
I can't compact and repair (C&R) the backend database. I tried
several times to C&R the database outside of normal working hours when
nobody is there. Don't get me wrong, the database will C&R
successfully, however, one or more tables in the database will then
stop accepting more records. For instance I have a table called
tbl_Account with 95K records, with one non-duplicate index primary key
field being Account and a non-duplicate index of field ID (see figure
1 below). If I try to add an account number that I know doesn't
exist, I just get an Access message saying a existing record already
exists in the table and the new record cannot be added. The database
doesn't seem to care which tables become corrupt. My error log
doesn't have any indexes, yet it became corrupt and it only has 20 or
so records. Most of the errors in the error log are 3000 level errors
which as you know are network related problems, thus my original post
in the first place to go with a pure HTML and ASP solution. The only
way that I can save the backend is to create a new database and import
all the objects, delete the old backend, rename the new backend, and
then set permissions.
Figure 1.
tbl_Account
---------------
Account Text(10)
ID AutoNumber
RecordCreated Date
RecordCreatedBy Text(15)
LastModified Date
LastModifiedBy Text(15)
The backend is Access 2000 format. The client machines run a combo of
Office 2000 and Office XP. There are five clients with mde files, and
two Admins that I allow to run mdb files. I have no idea if the
server is running Windows 2000 or XP but I can't just phone over to IT
to ask them to start fiddling with the server and adjust the OpLocks
properties because a lot of people use to the server outside of my
department running a variety of applications. Besides, I'll come off
as a lunch room conversation dumbass (we told you that Access sucks
Fred) from the IT department. Furthermore, I can't just go around to
the frontend clients and ask to kick them off their computers for
their lunch break to install service packs which may or may not be
backwards compatible with their existing applications. Sort of a my
cubicle = my domain = go away thing exists.
As for subforms, well they kind of suck to begin with in my own
opinion. Please don't launch some new thread in defense of subforms
but my experience with subforms is that frontend users find them
rather complicated. They don't understand/care to understand database
schema, specially, one to many relationships. Your right in saying
that HTML is more complicated because you can't have subforms (maybe
some guru could design a pure Java applet website with one) but it can
be done with good backend design, specifically, an ID (AutoNumber)
field in each table. Look at your personal address book on
Amazon.com. That is such an example of one to many written in HTML,
works perfectly, and is rather easy for frontend users to understand.
My point is that once you get up to 50 or so tables the database is
already complex. If you are the sole designer of the database you
should be able to follow your code, even spaghetti code such as ASP.
If you have a good web hosting company, a good internet connection,
solid backend design, and good code (objRS.close, etc...) then I think
that an HTML and ASP solution is the way to go. It hasn't failed me
yet.
Fred
Tony Toews <tt****@telusplanet.net> wrote in message news:
<ma********************************@4ax.com>... fm********@juno.com (Fred MacMurray) wrote:
I've spent the past couple days researching corruption because I am
constantly restoring backed up copies of my backend. Usually once a
week I have to restore a backup or create a new database and import
all the objects from the old database. This is getting to be a pain
because the database is a growing 500mb and making my coworkers pissed
off. Thank God that I have a redundant error logs (sometimes the
error log become corrupt!) to record when the backend is broke. I am
confident in my backend design and client VB code (over three years
experience writing/designing) but some tables in the database just
become corrupt by not allowing record additions. I'll try to add a
record myself, one that I know is unique, but still Access gives a
message that an existing record already exists in the table.
You sound fairly knowledgable so my commment is something you may already be aware
of. Are there unique indexes present on fields which aren't the primary index which
are causing the record additions to not be allowed?
From
reading corruption articles from this newsgroup and the Microsoft
website I've noticed that a lot of the corruption issues have to do
with hardware and networking equipment such as: faulty NIC's,
hibernation of client's PC's, intermittent network connections.
Not at all. The most common problem is the OpLocks problem which is especially
apparent when an app is converted to Access 2000 or newer or when the first Win 2000
client is added to a network consisting of a Win NT/2000/2003 server and until now
Win 95/98/ME clients.
Other problems can be caused by differing SR or Jet versions on clients. See the
Access Corruptions FAQ at my website.
So my question to all of you is the following: is the solution ASP?
Is the solution to use Access as a backend and use browser forms to
interact with the database? I've built three HTML and ASP websites
with Access as the backend and have never had any problems. Let me
reiterate, no problems at all. There would probably be performance
issues with over ten or so users but with less than ten users I think
it would be the way to go.
I don't think so because you lose the rich event model of Access, subforms and combo
boxes become uglier, and it's likely a lot more work.
Tony
I've implemented MS Access with ASP and it's a great approach - you
don't have the 'flexability' of the forms you would in Access or VB -
but you don't really lose much and the maintainability is great - no
need to ever visit a user workstation again - they just point to the
web site.....another approach would be Citrix - if you have the $ for
it. I've supported over 50 users with ASP and have had no performance
problems at all - I would expect being able to support up to 200
active prior to moving to a more robust database... fm********@juno.com (Fred MacMurray) wrote in message news:<74**************************@posting.google. com>... Tony,
I can't compact and repair (C&R) the backend database. I tried
several times to C&R the database outside of normal working hours when
nobody is there. Don't get me wrong, the database will C&R
successfully, however, one or more tables in the database will then
stop accepting more records. For instance I have a table called
tbl_Account with 95K records, with one non-duplicate index primary key
field being Account and a non-duplicate index of field ID (see figure
1 below). If I try to add an account number that I know doesn't
exist, I just get an Access message saying a existing record already
exists in the table and the new record cannot be added. The database
doesn't seem to care which tables become corrupt. My error log
doesn't have any indexes, yet it became corrupt and it only has 20 or
so records. Most of the errors in the error log are 3000 level errors
which as you know are network related problems, thus my original post
in the first place to go with a pure HTML and ASP solution. The only
way that I can save the backend is to create a new database and import
all the objects, delete the old backend, rename the new backend, and
then set permissions.
Figure 1.
tbl_Account
---------------
Account Text(10)
ID AutoNumber
RecordCreated Date
RecordCreatedBy Text(15)
LastModified Date
LastModifiedBy Text(15)
The backend is Access 2000 format. The client machines run a combo of
Office 2000 and Office XP. There are five clients with mde files, and
two Admins that I allow to run mdb files. I have no idea if the
server is running Windows 2000 or XP but I can't just phone over to IT
to ask them to start fiddling with the server and adjust the OpLocks
properties because a lot of people use to the server outside of my
department running a variety of applications. Besides, I'll come off
as a lunch room conversation dumbass (we told you that Access sucks
Fred) from the IT department. Furthermore, I can't just go around to
the frontend clients and ask to kick them off their computers for
their lunch break to install service packs which may or may not be
backwards compatible with their existing applications. Sort of a my
cubicle = my domain = go away thing exists.
As for subforms, well they kind of suck to begin with in my own
opinion. Please don't launch some new thread in defense of subforms
but my experience with subforms is that frontend users find them
rather complicated. They don't understand/care to understand database
schema, specially, one to many relationships. Your right in saying
that HTML is more complicated because you can't have subforms (maybe
some guru could design a pure Java applet website with one) but it can
be done with good backend design, specifically, an ID (AutoNumber)
field in each table. Look at your personal address book on
Amazon.com. That is such an example of one to many written in HTML,
works perfectly, and is rather easy for frontend users to understand.
My point is that once you get up to 50 or so tables the database is
already complex. If you are the sole designer of the database you
should be able to follow your code, even spaghetti code such as ASP.
If you have a good web hosting company, a good internet connection,
solid backend design, and good code (objRS.close, etc...) then I think
that an HTML and ASP solution is the way to go. It hasn't failed me
yet.
Fred
Tony Toews <tt****@telusplanet.net> wrote in message news:
<ma********************************@4ax.com>... fm********@juno.com (Fred MacMurray) wrote:
I've spent the past couple days researching corruption because I am
constantly restoring backed up copies of my backend. Usually once a
week I have to restore a backup or create a new database and import
all the objects from the old database. This is getting to be a pain
because the database is a growing 500mb and making my coworkers pissed
off. Thank God that I have a redundant error logs (sometimes the
error log become corrupt!) to record when the backend is broke. I am
confident in my backend design and client VB code (over three years
experience writing/designing) but some tables in the database just
become corrupt by not allowing record additions. I'll try to add a
record myself, one that I know is unique, but still Access gives a
message that an existing record already exists in the table.
You sound fairly knowledgable so my commment is something you may already be aware
of. Are there unique indexes present on fields which aren't the primary index which
are causing the record additions to not be allowed?
From
reading corruption articles from this newsgroup and the Microsoft
website I've noticed that a lot of the corruption issues have to do
with hardware and networking equipment such as: faulty NIC's,
hibernation of client's PC's, intermittent network connections.
Not at all. The most common problem is the OpLocks problem which is especially
apparent when an app is converted to Access 2000 or newer or when the first Win 2000
client is added to a network consisting of a Win NT/2000/2003 server and until now
Win 95/98/ME clients.
Other problems can be caused by differing SR or Jet versions on clients. See the
Access Corruptions FAQ at my website.
So my question to all of you is the following: is the solution ASP?
Is the solution to use Access as a backend and use browser forms to
interact with the database? I've built three HTML and ASP websites
with Access as the backend and have never had any problems. Let me
reiterate, no problems at all. There would probably be performance
issues with over ten or so users but with less than ten users I think
it would be the way to go.
I don't think so because you lose the rich event model of Access, subforms and combo
boxes become uglier, and it's likely a lot more work.
Tony
MeadeR,
See, that's what I am talking about! No more service pack hassles, no
more network and NIC troubleshooting, and no more running around to
client machines to install the latest frontends.
You really have 50 users hitting your backend at the same time? How
big is the mdb?
Fred Me****@ComputerSOSNJ.com (MeadeR) wrote in message news:
<32*************************@posting.google.com>.. . I've implemented MS Access with ASP and it's a great approach - you
don't have the 'flexability' of the forms you would in Access or VB -
but you don't really lose much and the maintainability is great - no
need to ever visit a user workstation again - they just point to the
web site.....another approach would be Citrix - if you have the $ for
it. I've supported over 50 users with ASP and have had no performance
problems at all - I would expect being able to support up to 200
active prior to moving to a more robust database...
fm********@juno.com (Fred MacMurray) wrote in message news:<74**************************@posting.google. com>... Tony,
I can't compact and repair (C&R) the backend database. I tried
several times to C&R the database outside of normal working hours when
nobody is there. Don't get me wrong, the database will C&R
successfully, however, one or more tables in the database will then
stop accepting more records. For instance I have a table called
tbl_Account with 95K records, with one non-duplicate index primary key
field being Account and a non-duplicate index of field ID (see figure
1 below). If I try to add an account number that I know doesn't
exist, I just get an Access message saying a existing record already
exists in the table and the new record cannot be added. The database
doesn't seem to care which tables become corrupt. My error log
doesn't have any indexes, yet it became corrupt and it only has 20 or
so records. Most of the errors in the error log are 3000 level errors
which as you know are network related problems, thus my original post
in the first place to go with a pure HTML and ASP solution. The only
way that I can save the backend is to create a new database and import
all the objects, delete the old backend, rename the new backend, and
then set permissions.
Figure 1.
tbl_Account
---------------
Account Text(10)
ID AutoNumber
RecordCreated Date
RecordCreatedBy Text(15)
LastModified Date
LastModifiedBy Text(15)
The backend is Access 2000 format. The client machines run a combo of
Office 2000 and Office XP. There are five clients with mde files, and
two Admins that I allow to run mdb files. I have no idea if the
server is running Windows 2000 or XP but I can't just phone over to IT
to ask them to start fiddling with the server and adjust the OpLocks
properties because a lot of people use to the server outside of my
department running a variety of applications. Besides, I'll come off
as a lunch room conversation dumbass (we told you that Access sucks
Fred) from the IT department. Furthermore, I can't just go around to
the frontend clients and ask to kick them off their computers for
their lunch break to install service packs which may or may not be
backwards compatible with their existing applications. Sort of a my
cubicle = my domain = go away thing exists.
As for subforms, well they kind of suck to begin with in my own
opinion. Please don't launch some new thread in defense of subforms
but my experience with subforms is that frontend users find them
rather complicated. They don't understand/care to understand database
schema, specially, one to many relationships. Your right in saying
that HTML is more complicated because you can't have subforms (maybe
some guru could design a pure Java applet website with one) but it can
be done with good backend design, specifically, an ID (AutoNumber)
field in each table. Look at your personal address book on
Amazon.com. That is such an example of one to many written in HTML,
works perfectly, and is rather easy for frontend users to understand.
My point is that once you get up to 50 or so tables the database is
already complex. If you are the sole designer of the database you
should be able to follow your code, even spaghetti code such as ASP.
If you have a good web hosting company, a good internet connection,
solid backend design, and good code (objRS.close, etc...) then I think
that an HTML and ASP solution is the way to go. It hasn't failed me
yet.
Fred
Tony Toews <tt****@telusplanet.net> wrote in message news:
<ma********************************@4ax.com>... fm********@juno.com (Fred MacMurray) wrote:
>I've spent the past couple days researching corruption because I am
>constantly restoring backed up copies of my backend. Usually once a
>week I have to restore a backup or create a new database and import
>all the objects from the old database. This is getting to be a pain
>because the database is a growing 500mb and making my coworkers pissed
>off. Thank God that I have a redundant error logs (sometimes the
>error log become corrupt!) to record when the backend is broke. I am
>confident in my backend design and client VB code (over three years
>experience writing/designing) but some tables in the database just
>become corrupt by not allowing record additions. I'll try to add a
>record myself, one that I know is unique, but still Access gives a
>message that an existing record already exists in the table.
You sound fairly knowledgable so my commment is something you may already be aware
of. Are there unique indexes present on fields which aren't the primary index which
are causing the record additions to not be allowed?
>From
>reading corruption articles from this newsgroup and the Microsoft
>website I've noticed that a lot of the corruption issues have to do
>with hardware and networking equipment such as: faulty NIC's,
>hibernation of client's PC's, intermittent network connections.
Not at all. The most common problem is the OpLocks problem which is especially
apparent when an app is converted to Access 2000 or newer or when the first Win 2000
client is added to a network consisting of a Win NT/2000/2003 server and until now
Win 95/98/ME clients.
Other problems can be caused by differing SR or Jet versions on clients. See the
Access Corruptions FAQ at my website.
>So my question to all of you is the following: is the solution ASP?
>Is the solution to use Access as a backend and use browser forms to
>interact with the database? I've built three HTML and ASP websites
>with Access as the backend and have never had any problems. Let me
>reiterate, no problems at all. There would probably be performance
>issues with over ten or so users but with less than ten users I think
>it would be the way to go.
I don't think so because you lose the rich event model of Access, subforms and combo
boxes become uglier, and it's likely a lot more work.
Tony
Yep - ASP - takes away allot of the hassles of workstation based
installations. I have 50 active users - probably 5-10 hitting the
backend at any one time. The mdb is about 100 megs, but it also
connects to about 20 SQL Server based tables. It's a combination
Incident tracking system, config management and release scheduling
system. I used Dreamweaver to develop the web side. fm********@juno.com (Fred MacMurray) wrote in message news:<74**************************@posting.google. com>... MeadeR,
See, that's what I am talking about! No more service pack hassles, no
more network and NIC troubleshooting, and no more running around to
client machines to install the latest frontends.
You really have 50 users hitting your backend at the same time? How
big is the mdb?
Fred
Me****@ComputerSOSNJ.com (MeadeR) wrote in message news:
<32*************************@posting.google.com>.. . I've implemented MS Access with ASP and it's a great approach - you
don't have the 'flexability' of the forms you would in Access or VB -
but you don't really lose much and the maintainability is great - no
need to ever visit a user workstation again - they just point to the
web site.....another approach would be Citrix - if you have the $ for
it. I've supported over 50 users with ASP and have had no performance
problems at all - I would expect being able to support up to 200
active prior to moving to a more robust database...
fm********@juno.com (Fred MacMurray) wrote in message news:<74**************************@posting.google. com>... Tony,
I can't compact and repair (C&R) the backend database. I tried
several times to C&R the database outside of normal working hours when
nobody is there. Don't get me wrong, the database will C&R
successfully, however, one or more tables in the database will then
stop accepting more records. For instance I have a table called
tbl_Account with 95K records, with one non-duplicate index primary key
field being Account and a non-duplicate index of field ID (see figure
1 below). If I try to add an account number that I know doesn't
exist, I just get an Access message saying a existing record already
exists in the table and the new record cannot be added. The database
doesn't seem to care which tables become corrupt. My error log
doesn't have any indexes, yet it became corrupt and it only has 20 or
so records. Most of the errors in the error log are 3000 level errors
which as you know are network related problems, thus my original post
in the first place to go with a pure HTML and ASP solution. The only
way that I can save the backend is to create a new database and import
all the objects, delete the old backend, rename the new backend, and
then set permissions.
Figure 1.
tbl_Account
---------------
Account Text(10)
ID AutoNumber
RecordCreated Date
RecordCreatedBy Text(15)
LastModified Date
LastModifiedBy Text(15)
The backend is Access 2000 format. The client machines run a combo of
Office 2000 and Office XP. There are five clients with mde files, and
two Admins that I allow to run mdb files. I have no idea if the
server is running Windows 2000 or XP but I can't just phone over to IT
to ask them to start fiddling with the server and adjust the OpLocks
properties because a lot of people use to the server outside of my
department running a variety of applications. Besides, I'll come off
as a lunch room conversation dumbass (we told you that Access sucks
Fred) from the IT department. Furthermore, I can't just go around to
the frontend clients and ask to kick them off their computers for
their lunch break to install service packs which may or may not be
backwards compatible with their existing applications. Sort of a my
cubicle = my domain = go away thing exists.
As for subforms, well they kind of suck to begin with in my own
opinion. Please don't launch some new thread in defense of subforms
but my experience with subforms is that frontend users find them
rather complicated. They don't understand/care to understand database
schema, specially, one to many relationships. Your right in saying
that HTML is more complicated because you can't have subforms (maybe
some guru could design a pure Java applet website with one) but it can
be done with good backend design, specifically, an ID (AutoNumber)
field in each table. Look at your personal address book on
Amazon.com. That is such an example of one to many written in HTML,
works perfectly, and is rather easy for frontend users to understand.
My point is that once you get up to 50 or so tables the database is
already complex. If you are the sole designer of the database you
should be able to follow your code, even spaghetti code such as ASP.
If you have a good web hosting company, a good internet connection,
solid backend design, and good code (objRS.close, etc...) then I think
that an HTML and ASP solution is the way to go. It hasn't failed me
yet.
Fred
Tony Toews <tt****@telusplanet.net> wrote in message news:
<ma********************************@4ax.com>...
> fm********@juno.com (Fred MacMurray) wrote:
>
> >I've spent the past couple days researching corruption because I am
> >constantly restoring backed up copies of my backend. Usually once a
> >week I have to restore a backup or create a new database and import
> >all the objects from the old database. This is getting to be a pain
> >because the database is a growing 500mb and making my coworkers pissed
> >off. Thank God that I have a redundant error logs (sometimes the
> >error log become corrupt!) to record when the backend is broke. I am
> >confident in my backend design and client VB code (over three years
> >experience writing/designing) but some tables in the database just
> >become corrupt by not allowing record additions. I'll try to add a
> >record myself, one that I know is unique, but still Access gives a
> >message that an existing record already exists in the table.
>
> You sound fairly knowledgable so my commment is something you may already be aware
> of. Are there unique indexes present on fields which aren't the primary index which
> are causing the record additions to not be allowed?
>
> >From
> >reading corruption articles from this newsgroup and the Microsoft
> >website I've noticed that a lot of the corruption issues have to do
> >with hardware and networking equipment such as: faulty NIC's,
> >hibernation of client's PC's, intermittent network connections.
>
> Not at all. The most common problem is the OpLocks problem which is especially
> apparent when an app is converted to Access 2000 or newer or when the first Win 2000
> client is added to a network consisting of a Win NT/2000/2003 server and until now
> Win 95/98/ME clients.
>
> Other problems can be caused by differing SR or Jet versions on clients. See the
> Access Corruptions FAQ at my website.
>
> >So my question to all of you is the following: is the solution ASP?
> >Is the solution to use Access as a backend and use browser forms to
> >interact with the database? I've built three HTML and ASP websites
> >with Access as the backend and have never had any problems. Let me
> >reiterate, no problems at all. There would probably be performance
> >issues with over ten or so users but with less than ten users I think
> >it would be the way to go.
>
> I don't think so because you lose the rich event model of Access, subforms and combo
> boxes become uglier, and it's likely a lot more work.
>
> Tony This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Noa Garnett |
last post by:
I'm developing on C++, using visual studio 6.0 with service pack 5.
I have a memory corruption while debugging. Some of the variables I'm
using are suddenly set to zero while progressing along the...
|
by: Mark C. |
last post by:
The company I work for has been running Access 2000 on a Windows NT
server with Opportunistic Locking turned off on the server without
issue for almost a year. We have just switched to a Windows...
|
by: Mike |
last post by:
I have done a lot of research on DAO and database corruption and have
not yet found any solid information for my problem. I use DAO
extensively in my Access 97 databases (back-end on network,...
|
by: DFS |
last post by:
" has detected corruption in this file. To try to repair the
corruption, first make a backup copy of the file. Then, on the Tools menu,
point to Database Utilities and click Compact and Repair...
|
by: ship |
last post by:
Hi
We need some advice: We are thinking of upgrading our Access database
from Access 2000 to Access 2004.
How stable is MS Office 2003? (particularly Access 2003).
We are just a small...
|
by: ranjeet.gupta |
last post by:
Dear All
Is the Root Cause of the Memory corruption is the Memory leak, ??
suppose If in the code there is Memory leak, Do this may lead to the
Memory Corruption while executing the program ?
...
|
by: Dave G |
last post by:
Since upgrading one of my clients from A97/W2000 to A2003/XP they have
suffered no end of data corruption problems, mainly involving one of
the main tables. The corruption can result in one...
|
by: nepdae |
last post by:
Please forgive me, this is a long one.
My 11-user Access 2000 database is having recurring corruption
problems. The symptoms include the following:
1) corrupted fields in recently created or...
|
by: Doug |
last post by:
I am in a friendly debate with some co-workers... and my boss.
We use Access 2003 for the frontend (on workstations) as well as for
the backend (on a Dell PowerEdge running Windows 2000 server,...
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |
