Recent content by rpatel18

So I can just keep the table with all the 74 cats in them(column 1) and make the zip code primary on that table(column2) and just make a one to many relationship? If this is the case, i feel like an idiot then....lol

so should I just use a one to many relationship?

I dont see how I would only need two tables with 74 categories all containing 30,000+ zip codes. The 74 categories also have to be linked to IRS data and census data both with the primary key of zipcodes.

well, each subcat has all the zip codes in the US with certain information regarding that zip code. All the other data has a primary key of zipcodes, splitting the table apart would let me link to those sub cats.

how would I loop 74 different queries?

I just used the build querey feature in access and edited it. I have limited knowledge about access and sql. I'm only a intern and a college sophmore trying to compile databases and create reporting tools for the company I work for.

all of them aren't the same, they are slightly different. I have 74 subcategories in one table, and I need to split all those 74 subcatogories into their own tables.

they all run fine individually but i dont feel like running 74 individual queries.

I'm trying to split a table into multiple tables. The code I'm using is the following but I keep getting a syntax error in querey expression. SELECT [2004 Retail].NAIC, [2004 Retail].[ZIP Code], [2004 Retail].[Total Establishments], [2004 Retail].[1-4], [2004 Retail].[5-9], [2004...

I used this macro: Sub RunCodeOnAllXLSFiles() Dim i As Integer Dim wbResults As Workbook Dim wbCodeBook As Workbook Application.ScreenUpdating = False Application.DisplayAlerts = False Application.EnableEvents = False On Error Resume Next Set...

I have the following macro in excel.. Sub replace() ' ' replace Macro ' Macro recorded 6/18/2007 by LISC USER ' Range("B1:CM4000").Select Selection.replace What:="** ", Replacement:="", LookAt:=xlPart, _ SearchOrder:=xlByRows, MatchCase:=False, SearchFormat:=False, _...

DTS?

well, I have it in excel, and import it to access(more comfortable working in access), and then it'll get imported to sql server.

I'm going to try and normalize the data in excel(came in excel format), take out all the none numerical values since there should only be numbers in there(many fields have $,-, and *) and then try to re-import them. I think the issue is I can't combine them because some fields are text fields in...

the fields right now are defined as text fields but they only contain numbers.