I have an interesting problem, and I wonder if anyone else has had the same effect: I created a FE/BE database at home in Access 2000 under Win 2000, with the latest versions of Jet and of the service packs. It ran well on my machine and on my client's network, where the Front-ends all ran on...
Maybe it is worth adding that when I move from one display to another, I change the recordsource of the form to an empty table, delete the records from my original display table, recreate the display table with the new data the user wants, and then change the recordsource back to the display...
Hi,
Yes, it is a continuous form. There are no subforms, and because of the potential for 32 columns of size data, the form is very wide (a little over 2 screens of 1024 X 768). It can be from 1 record (about half an inch in depth) to 100 records long (vertically). So it is a big form!
Mark
I have created a form that shows the user how much inventory is available at a given time for a given product or a category of products. They can then take an order for the quantity of the particular colour of product the client wants.
Because the size range can vary from inquiry to inquiry...
That is a very interesting approach, Jim. I hadn't noticed that we had that sort of error-trapping ability. I will just have to add a flag to specify that we have just entered a date field (so the standard errors come out elsewhere, if they are needed), and I am set.
Thanks a lot to you, and to...
I'm afraid all of your "staws" don't work or don't apply; this triggers after the On Change, but I don't think there is a reasonable way to know that we have come to the end of the typing in this field (maybe watch for tabs, Enter, Return, Arrows....)
Thanks for the attempts.
The field is set to Date in the table, and that seems to be where the problem is: it rejects the data if it is not a date with a generic message (i.e. "The value you entered is not valid for this field") rather than the custom message that I would like to have appear, which might be...
John: thanks for the idea, but like the BeforeUpdate, it is triggered AFTER the table validates that this is not in proper date format.
Jim: I agree entirely, but am having troubling formulating the code to ensure that it is a date, and thus trigger the validation text if it is not. For...
Alternately, is there a way to issue my own message rather than the input mask error message that says that "The value entered does not match a mask of type #9\->L<LL\-00;0".
That is not the most helpful message to offer!
Mark
I am trying to validate dates in a manner that is easier for the user than the input masks. But when I try to use an ISDATE(me!txtDate) in the BeforeUpdate event of my form, Access 2000 rejects the bad data before it gets to the BeforeUpdate. It seems to be seeing that the data is not a date...
I found a solution to my problems via Tony Toews at http://www.granite.ab.ca/access/a2kslow.htm. As his site is not always up, I will reproduce his key statements below:
"When the symptoms encountered indicate that performance is acceptable with a single user in the database but drops...
I have a front-end/back-end database made up of about 10 related tables; I have been working to speed it up, and thought I had it working fine.
I have just found out, however, that when I open a two copies of the database on separate workstations (connected by 100-base ethernet to a Win2000...
Not according to Microsoft; their topic Q208735 (http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q208735) says that the information in their help system that said it WAS faster is incorrect.
My own testing also shows that it is not any faster.
Good luck!
Mark
In thread181-31163, one repondent suggests that often networks can be tweeked to make it better for databases (rather than being optimized for email and file transfers). Can someone tell me how to do this, and whether this can be done with Windows ME? (Our Access backend is being served (for the...
I have a front end/back end Access 2000 db with 5 users, with 16 tables, and approx 450 records in the main table. A single user (all alone, no one else in the office, no other programs open) opens the form which accesses the main table (and links to several of the others; each link is on a...
There is likely some bad data in that record. I would export all of the other records using a query (or simply copy-paste) to a new table (maybe you can create a copy of the table with no data in it). Then you can delete your original corrupted table.
I have never tried Analyze before; I will try it. In the meantime, I have found two Microsoft documents that were of some help:
1) How to Troubleshoot/Repair a Damaged Jet 4.0 Database (Knowledgebase Article Q209137...
On second thought, I don't think it can be the back end, because I gave a user an older version of the front end to use, and she got faster results. What I will try is relinking the tables (between the front- and the back-ends), to see if that helps. I have also added one table to the front end...
Thanks; I will try this. I had been presuming that the problems were likely in my front end, and trying to figure out how to clean it up. I won't really know whether it worked until early next week when I am on the client's network again.
Mark
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.