Nicholson, Karen
cyx5 at cdc.gov
Thu Dec 23 12:35:28 CST 2004
Wouldn't I love that? This is a process that was put into place a long time ago and is *working*. My plan is to present to them a good database to management, then proposing the idea that the manufacturers should be using a nice little database to present their data to us that we can distribute over the web so they have access to their most recent parts file. Imagine this - each of these manufacturers has to maintain their own data source of their current items and we have over 400 manufacturers. These people are not database people, more like Word folks. One step at a time, one success at a time. Everything that I have done for them has improved their lives and ticked them off as they spent so much money on junk databases for years. I am in a win-win situation. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Thursday, December 23, 2004 1:27 PM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Capture That Record Number Karen, Could 'Susie' enter the parts using a form designed for that purpose? I guess the data could go to a 'NewInfo' table. The form could have some data validation where appropriate, and you could avoid the spreadsheet altogether. Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, Karen Sent: Thursday, December 23, 2004 11:36 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Capture That Record Number I have a parts database, it was 855 databases, I have now put it into one. Nimrods. Manufacturers submit via the excel spreadsheet from he** new "assemblies" that can contain up to 850 parts. So, Susie "Data Entry I Broke a Fingernail", enters in the part numbers and descriptions into this excel spreadsheet. I transfer the spreadsheet into SQL backend, then compare the part number and various fields to what we have on the official file and compare it to Susie Fingernail's spreadsheet. I hook the information in the official parts database to the new junk that is sent to us and display those records on a form where there are discrepancies in about 5 different fields. There is category name, drawing number, revision level, description and model number. On the form, they can press a button to change Susie's data to what is in the parts database. Then we have a match! So it is no longer in the datasource. Does that make sense? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, December 23, 2004 12:24 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Capture That Record Number It is simply an ordinal position in the recordset, not a real number. You can find out what the absolute position of the current record is when you enter it, but that's all. When you requery, the order of records may change, since new records are initially added to the end but will sort themselves appropriately on a requery. Why are you requerying after a delete? Charlotte Foust -----Original Message----- From: Nicholson, Karen [mailto:cyx5 at cdc.gov] Sent: Thursday, December 23, 2004 9:10 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Capture That Record Number That is what I did, but sometimes when I do the requery, then the record that I change eliminates it from the recordsource and when I tell it to go to that specific task number, it is not there. So I thought it would be nice to go to about the same place as before, or the record after the one that was deleted. There must be a place that the navigator bar gets its count from. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, December 23, 2004 11:48 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Capture That Record Number You don't. Access doesn't use record numbers in the sense that dBase does. It uses unique keys and the record "numbers" are just position indicators within the recordset. Those numbers can change after a requery. Instead, capture the unique key for that record and store it in a variable. Then find that key again in the form's recordsetclone after the requery and set the form's bookmark to the recordsetclone's bookmark. Hey, presto. Charlotte Foust -----Original Message----- From: Nicholson, Karen [mailto:cyx5 at cdc.gov] Sent: Thursday, December 23, 2004 8:41 AM To: accessd at databaseadvisors.com Subject: [AccessD] Capture That Record Number I am an active puppy today. How do you catch the record number on a continuous form so one can return to that record number after a requery is done? I can see only the higher minds are working today. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com