ACCESS FEED: RE: [MS_AccessPros] Event at the end of all entries on form including subforms?

Jumat, 21 Oktober 2011

RE: [MS_AccessPros] Event at the end of all entries on form including subforms?

Stuart-

Quotes and Orders could be in the same table - you end up eventually turning
some of them into actual orders. But since you have millions of quotes and only
a few of them turn into actual orders (ever wonder why so few?), it makes sense
to put them in separate tables both logistically and for performance reasons.
You should be linking the order back to its originating quote, however.

John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)

-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Stuart Luckman
Sent: Friday, October 21, 2011 10:17 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Event at the end of all entries on form including
subforms?

Hi,

I I have made our quote, orders and invoicing tables seperate due to the
massive size of the quotes table (million + records), medium size of the
orders table and small size of the invoice table.

I thought that by doing this I would be increasing performance of queries on
the invoice table, would this be a legitimate reason for doing what Connie
has been doing or would this be just poor design??

I'm learning as I go, and thought I'd reply here as it seemed related.

Cheers,

Stuart

From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of John Viescas
Sent: Friday, 21 October 2011 4:53 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Event at the end of all entries on form
including subforms?

Connie-

That's a toughie. I seem to recall that when a listing is sold, you actually
copy or move the record to a "sales" table. Is that correct? If you're
marking
the property "sold" (by entering a sales price and date) in the listings
record,
that makes it a bit easier. Which is the case?

John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)

-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
[mailto:MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com> ] On Behalf Of mrsgoudge
Sent: Thursday, October 20, 2011 10:25 PM
To: MS_Access_Professionals@yahoogroups.com
<mailto:MS_Access_Professionals%40yahoogroups.com>
Subject: [MS_AccessPros] Event at the end of all entries on form including
subforms?

I want to remind the user to enter the Market Value for the current year if
they
have entered the selling price and date and have not entered the Market
Value.
The selling price and date are entered on the Sales form and are elements of
the
sales table. The Market Value is a separate table and a subform for it is on
the Sales form. Ideally I would like the code to engage after the user has
entered all the data she thinks is needed. The Market Value subform is the
last
in the tab order. So the user first enters the Sales table date, then the
ListingContacts subform,and the Buyers subform before getting to the Market
Value table. Is there any event that fits this???

I am wanting to do this since finding that if the last years Market Value
was
the same as this years it is often not being entered for the current year
which
is necessary for accurate data ...

The code is below. I just haven't found the right event to use it in. May
need
to change it--Dlookup finds the first entry not all of them, right? But my
question above is still applicable

thanks!
Connie

If Not IsNull(Me.SoldPrice And Me.SoldDate) And DLookup("MVYear",
"MarketValue",
"HomeInfoID = " & Me.HomeInfoID) <> Year(Date) Then
Msgbox "A 2011 Market Value should be entered." _
& vbNewLine & "If you don't have it, enter this as a task on the Access To
Do
list."

If Not IsLoaded("Listings") Then
DoCmd.OpenForm "Listings", , "ListID = " & Me.ListID
Else:
DoCmd.FindRecord (Me.ListID)
End If
End If

------------------------------------

Yahoo! Groups Links

[Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links