Search results

ok- FYI- SELECT tbTempImport.ADDRESS, tbTempImport.AREA, tbTempImport.ST, tbTempImport.LP, tbTempImport.SP, qryAvgSoldinArea.AvgOfSP FROM tbTempImport, qryAvgSoldinArea WHERE (((tbTempImport.ST)="ACT")); and the other- SELECT tbTempImport.AREA, tbTempImport.ST, Avg(tbTempImport.SP) AS AvgOfSP...

Well- I made a simple db to work with as an example. I've been playing around with it- and THINK I figured out a way to do it. I made a simple query first that takes the average of all the areas. I then created a 2nd query that uses THAT expression, and then included a Criteria like this...

Yeah, it's repeating each record about 11 times... but then each group of 11 is repeated throughout the results- it's very odd what's going on. Any ideas?

YES! THAT WAS IT (I think!)- it SEEMS to be working! Here's the SQL- SELECT tbTempImport.ADDRESS, tbTempImport.AREA, tbTempImport.ST, tbTempImport.SP, qryAvgSoldinArea.AvgOfSP FROM tbTempImport, qryAvgSoldinArea WHERE (((tbTempImport.ST)="CLOSD")); HOWEVER- I have a bunch of repeated records...

Ron- Not saying you're wrong by any means- but- I'm not sure a report is what I'm looking for. Eventually, this basic query will be fairly complex- limiting it down to a size range, year range, whether or not the property is 1 or 2 stories, etc etc. Then I need to be able to access the results...

Hey guys- Been trying to figure this out, but am stuck. Obviously I'm fairly new to Access... I have a table of properties and the price those properties sold for. Each property is in a specific area of town. I want to take each record and display the Address, Area of town, Price it sold for...

ok- read that, and have a better feel for it now. So- seems like to me- Status (Active, Sold, Etc) does NOT need it's own table- I'll just include that in nearly every query I run. However- Realtor's info (name, code, phone #, etc) DOES need it's own table- especially since a realtor can...

How do I know when I should split a db into multiple tables? Right now- everything is in one table. Is there a rule of thumb or method to determine when I should split it up? For example- MY DB is running queries on properties for sale. Would I split all the Active, Sold, Expired, Off Market...

Awesome- Let me ask you something here... Should I split this DB into front/back ends? It's going to be fairly large, with 100s of thousands of records at any given time. The daily update file will be quite large as well. However, I will be the only user at any given time. Just not sure which...

Well- I believe it's the 2nd. Basically, there are 30,000+ records I need to apply this query to. Then, take THOSE results, and sort them Descending in a grid somewhere- so I can focus on just the top ones. But, yes, each record needs to have this query applied to it in order to determine the...

Ahhh- ok- makes sense. Things like +/- sf range (I could change on the fly), or other criteria... makes sense. Now, we're talking THOUSANDS of records at any given time. Does that change anything on this method?

Right- I would deliniate from there down. I definitely need to take into account the sf range, age, beds/bath, age, etc. Just trying to get the concept down first- then I can include all that in my queries. From a size/speed viewpoint- which is a better way to go? Run the calculations on the...

Hey guys- I have a database of properties for sale. I want to calculate the asking prices of each record (for sale) against the sold prices of all the houses in the same area. Area is defined as a numeric number, and each property has one assigned to it. My question is this- I have a table of...

ok- just so that I am clear... I understand the first part of having 2 tables (hunk of junk and good one). I would then have a separate table to store all the variations of the subdivision names in them. It might look like this: BadName GoodName The Willows The...

Hey guys- I am building a database for my own use- I download info from the Realtor MLS system and then run queries against it. I don't have control over user inputs whatsoever. I download the data into a DBF file- but can save it as an excel or whatever as well. I then am importing THAT data...

Hey guys- New here, and fairly new to Access as well (although I can stumble my way around). I am building a database in which I have to import the data on a daily basis (there won't be much, if any, data entry- just manipulating/Queries of the imported data). One of the fields I am importing is...