Drilling Down
Software: Bug Report
If you're experiencing a problem with our
Microsoft Access application, you're lying. Just
kidding!!! Go
ahead and tell me about it using the bug report form. There are no
outstanding requests for fixes at this time. You may want to check out the list of
fixed problems.
If what's on your mind is more
of a comment on the site itself, please use the suggestion form instead.
Please be as specific as possible when describing
the problem.
We may need to contact you for more information, such as if we have trouble reproducing the
problem you describe.
Back to Top
Known
Outstanding Problems
None.
Resolved
Problems or Desires / History
Number Three:
On 9/5/02, we released a
modification which resolved a problem some people were having with
larger databases blowing up the app. Now, we
never claimed you could cram a huge database through Access, and we
were told not to have much hope over 100,000 rows of data or so.
Still, depends on your set-up I suppose, so if you break the 100K row
mark with the app, shoot me an
e-mail, will ya? The Access 97 version was not and will not be
modified for large databases.
Number Two:
On 3/27/02, we released
version 1.2, which resolved a "problem" people were having
with non-numeric characters in the Customer ID field. Originally,
we intentionally restricted this field to numeric characters to
help prevent the pain people may experience down the road from using
non-numeric info in this field. Please, talk to your IT people
about this issue.
But the customer is always
right, so you get what you asked for in this release. For small
biz people testing a lot of new ideas, providing this option can make a
lot of sense - it is simply easier to deal with the process when you can
use "anything" for a Customer ID in your database.
Companies facing longer-term issues might think twice about using this
approach.
Only the Access 2000
version of the application has this extended character set
capability. The Access 1997 version does not and will not be
updated to include it.
Number 1:
A
permission problem with Microsoft Access 2000 was reported on 12/5/00; it
was resolved on 12/5/00. Permission parameters have been modified and
an additional file is now included with the download package so the
program will work equally well with Access 97 or Access 2000 under
various configurations.