Thanks AD, but when I follow your link the page says 'an error has occured. please try again'.
I've never used Windows Live, or Sky Drive...what do I need to do! Do you need to share the file with me?
Nige
--- In MS_Access_Professionals@yahoogroups.com, "A.D. Tejpal" <adtp@...> wrote:
>
> Nige,
>
> For a given sale order, requiring shipment of x units, if you find it more convenient to be presented with a grid having x rows of potential new records for entering unit-wise shipping, an interesting way could be considered for providing the desired functionality.
>
> Using a non-linked subform, a matrix of required number of virtual new records (matching batch size for the order in question) gets generated. This arrangement has the advantage that while the user can see at a glance all the available data entry slots, no record actually gets inserted in the source table until some real data (e.g. SerialNumber in your case) is actually entered. Despite full display of all candidate rows, this arrangement prevents insertion of any redundant / unused record.
>
> For ready reference, my sample db named Form_VirtualRecordsMatrix.zip, uploaded to WindowsLive SkyDrive (Uploading to our group's files section seems to be disabled at present), demonstrates the approach outlined above. PartNumber, SDN, SDN_Dt and BatchSize (number of units to be shipped) are displayed in the parent form, bound to table T_Orders, while the subform is fed by query Q_SalesMatrix whose primary source is table T_Despatches.
>
> On the subform, only one field (SerialNumber) is required to be filled in. Values for other two fields (BatchID and DespDtStamp) get inserted automatically. BatchID on the subform identifies PartNumber, SDN, SDN_Dt etc and there is no need to duplicate such information in table T_Despatches. For reporting purposes, if combined output of the two tables (T_Orders and T_Despatches) is needed, suitable query like Q_Despatches can be used.
>
> Note:
> ------
> Driver table T_DespNum is used for generating multiple rows of virtual records as needed. This table has a single field DespatchNum, populated with sequential numbers 1 to 300. If maximum BatchSize (number of units to be shipped against a single order) is likely to exceed 300, the driver table can be expanded suitably.
>
> Link to WindowsLiveSkyDrive is given below:
> -----------------------------------------------
> https://skydrive.live.com/?docsf=1&BICIRefSrc=OLW&BICIRefPub=SDX.Docs&sc=documents#!/?cid=9e4e658e6573b51a&sc=documents&uc=1&id=9E4E658E6573B51A%21109!cid=9E4E658E6573B51A&id=9E4E658E6573B51A%21109&sc=documents
>
> Best wishes,
> A.D. Tejpal
> ------------
>
> ----- Original Message -----
> From: nigelhjackson
> To: MS_Access_Professionals@yahoogroups.com
> Sent: Friday, September 23, 2011 19:34
> Subject: Re: [MS_AccessPros] How to speed up data entry - entry several rows of data from 1 simple form?
>
>
> Sorry!
>
> For each shipment (which has an SDNNumber (sales delivery note number) and SDNDate) there will normally be a single part number, and either many SerialNumbers each with Quantity 1, or where parts are not serialized, just 1 row with SerialNumber being blank and Quantity showing the relevant number.
>
> Very very rarely, a SDN may have 2 different parts on it.
>
> Does that make more sense now?
>
> Nige
>
> --- In MS_Access_Professionals@yahoogroups.com, Duane Hookom <duanehookom@> wrote:
> >
> >
> > Nige,
> > I'm not sure anyone can help you unless you describe your process of shipping etc. If you have lots of repeating values in tblSerialAndSDN, you might want to create a tblShipments and store those fields in the new table and then the primary key from tblShipments in tblSerialAndSDN.
> >
> > I'm not sure though since I don't know anything about your business processes etc.
> >
> > Duane Hookom
> > MS Access MVP
> >
> >
> >
> > To: MS_Access_Professionals@yahoogroups.com
> > From: nigel@
> > Date: Fri, 23 Sep 2011 08:27:09 +0000
> > Subject: Re: [MS_AccessPros] How to speed up data entry - entry several rows of data from 1 simple form?
> >
> > Thanks Duane,
> >
> > The database is really simple, so changing the structure is no issue for me.
> >
> > There are 2 tables...
> >
> > tblPartDetails - fields are - ID, Customer, PartNumber, PartDescription, WarrantyPeriodMonths, WarrantyPeriodDays
> > tblSerialAndSDN - fields are - ID, SerialNumber, PartNumber, SDNNumber, SDNDate, WarrantyPeriodDays, Quantity
> > 1 form to enter/view/filter the data
> > 1 report
> >
> > I think I'll get rid of the WarrantyPeriodMonths field as I'm not using it after all.
> >
> > Customer, PartNumber, PartDescription, WarrantyPeriodDays are included in a combo box on the form - once a selection is made the part number is inserted into the form field and table field, and WarrantyPeriodDays inserted into a hidden form field and the table field.
> >
> > WarrantyPeriodDays is duplicated like this in tblSerialAndSDN as I need to use it in the calculation of form fields WarrantyExpiryDate and WarrantyDaysLeft but I couldn't do that unless I used the value from the combo after inserting it into the field/table...I'm sure there is a way, but with my very limited knowledge I couldn't find it!!!
> >
> > Your suggestion sounds very sensible, but I'm not sure what I need to do to make it happen. Could you give me some more info please?
> >
> > Cheers, Nige
> >
> > --- In MS_Access_Professionals@yahoogroups.com, Duane Hookom <duanehookom@> wrote:
> > >
> > >
> > > Nige,
> > >
> > > Based on "shipment of 150 units" and "select part number and enter SDN number and date for each row, when they are all the same!" I would review the table structure where there might be this much repeating information. I don't know what your table structure is but have you considered a shipment header table with the SDN and shipment date and a shipment detail table with the shipment ID and part number?
> > >
> > > If you don't want to change your table structure, you can use a main form with SDN and Shipment Date and a subform with your current table. Set the Link Master and Link Child properties to the SDN adn Shipment Date. This will automatically default the values in the subform to the values from the main form.
> > >
> > > Duane Hookom
> > > MS Access MVP
>
> > >
> > > From: nigel@
> > >
> > > Thanks Bill and Paul for your help - everything in my simple warranty database is now working as intended!
> > >
> > > Now...I have new records added one row at a time...a user clicks 'add new' to get a blank row, enters the serial number, selects the part number from a combo box, enters the SDN (delivery note) number and enters the SDN date.
> > >
> > > That's all great, until despatch have a shipment of 150 units, then it's laborious having to select part number and enter SDN number and date for each row, when they are all the same!
> > >
> > > So...I'd like to create a new form 'enter shipment' in which the user selects the part number and enters SDN number and date at the top, only once, then in a text or memo field enters all serial numbers on separate rows (by scanning bar codes, so very quick), then hit 'submit' and the database creates rows in the table for each serial number that has been scanned, using the part/sdn/date data for each.
> > >
> > > But, as usual, I don't know how to achieve this, so can someone point me in the right direction?
> > >
> > > Cheers, Nige
>
> [Non-text portions of this message have been removed]
>
Tidak ada komentar:
Posting Komentar