seeking a field

  • Thread starter Thread starter ManhattanRebel
  • Start date Start date
M

ManhattanRebel

In design view, how can I easily go to a specified column?

Also, why does the cursor go back to column 1 after I enter a new column?

Thx.
Rebel
 
In design view, how can I easily go to a specified column?

In design view of... WHAT? What do you mean by "go to"? What's the context:
what do you have in the database and what are you trying to accomplish?
Also, why does the cursor go back to column 1 after I enter a new column?

It doesn't, for me, not when I'm constructing a query or a form or a report.
It's not clear to me what is "going" where.
 
John W. Vinson said:
In design view of... WHAT? What do you mean by "go to"? What's the context:
what do you have in the database and what are you trying to accomplish?


It doesn't, for me, not when I'm constructing a query or a form or a report.
It's not clear to me what is "going" where.

OK. Forget Design View.
If I'm in Database View in a Table, and I have several fields with different
headings, how do I specify that I want to go to one of the 100 fields by
field name?

I would ultimately like to sort that field AtoZ, then make new field
headings that match the text content of the field. There are usually 4 to 15
different text names in that field. Once I make the new fields with new
names, I would like to copy the text from the rows under that initial field
and paste it into the new fields under which it matches. For instance, with
initial field of "Names", I would make four new fields with headings of
"John", "Susan", "Mark", etc. Then I want for all the "Mark's" under the
Name field heading be copied and pasted in the same row to the column named
"Mark".

Thanks.
 
OK. Forget Design View.
If I'm in Database View in a Table, and I have several fields with different
headings, how do I specify that I want to go to one of the 100 fields by
field name?

If you have 100 fields in your table, you don't have a table - you have a
spreadsheet. Storing data (such as "John", "Susan", "Mark") in a fieldname IS
SIMPLY INCORRECT DESIGN.

You can "rotate" a tall thin table with fields for FirstName and other data
into a wide-flat view with a FirstName at the head of each column by using a
Crosstab Query, but you would certainly never want to create a *table* with
that structure.
I would ultimately like to sort that field AtoZ, then make new field
headings that match the text content of the field. There are usually 4 to 15
different text names in that field. Once I make the new fields with new
names, I would like to copy the text from the rows under that initial field
and paste it into the new fields under which it matches. For instance, with
initial field of "Names", I would make four new fields with headings of
"John", "Susan", "Mark", etc. Then I want for all the "Mark's" under the
Name field heading be copied and pasted in the same row to the column named
"Mark".

If you'll step back and describe the nature of the data and what you're trying
to accomplish in a real world sense, someone should be able to suggest a
normalized solution. It will NOT involve fields named "Mark", "Matthew",
"Luke", or "John".
 
John W. Vinson said:
If you have 100 fields in your table, you don't have a table - you have a
spreadsheet. Storing data (such as "John", "Susan", "Mark") in a fieldname IS
SIMPLY INCORRECT DESIGN.

You can "rotate" a tall thin table with fields for FirstName and other data
into a wide-flat view with a FirstName at the head of each column by using a
Crosstab Query, but you would certainly never want to create a *table* with
that structure.


If you'll step back and describe the nature of the data and what you're trying
to accomplish in a real world sense, someone should be able to suggest a
normalized solution. It will NOT involve fields named "Mark", "Matthew",
"Luke", or "John".

You are correct. I am working on a spreadsheet that was imported from
Excel. I put the contents into a table, and I want to create several new
fields to where I can transfer data that is currently under one field. I
used the example "Names" earlier, but it's actually "Tracking Charge" and the
data runs anywhere from "Additional Handling", and "Address Correction" to
"Fuel Surcharge". Sometimes there are four data items and sometimes there
are fifteen. It depends on what my client downloads to me each week.

I just want to take those data items and create new fields for each one just
next to the field they are in now ("Tracking Charge"). Once a column, or
field, is established with a new heading, I want to move the data name (e.g.
"Fuel Surcharge") to the new field. I just want to move it over. In other
words, you will be left with a new field titled "Fuel Surcharge" and below
that, maybe rows 45 through 95 will have the same thing: "Fuel Surcharge".
The next column or field will be headed "Saturday delivery" and rows 96
through 130, for example, will also say: "Saturday delivery".

This may work better or easier in Excel for all I know.

Thanks.
 
You are correct. I am working on a spreadsheet that was imported from
Excel. I put the contents into a table, and I want to create several new
fields to where I can transfer data that is currently under one field. I
used the example "Names" earlier, but it's actually "Tracking Charge" and the
data runs anywhere from "Additional Handling", and "Address Correction" to
"Fuel Surcharge". Sometimes there are four data items and sometimes there
are fifteen. It depends on what my client downloads to me each week.

I just want to take those data items and create new fields for each one just
next to the field they are in now ("Tracking Charge"). Once a column, or
field, is established with a new heading, I want to move the data name (e.g.
"Fuel Surcharge") to the new field. I just want to move it over. In other
words, you will be left with a new field titled "Fuel Surcharge" and below
that, maybe rows 45 through 95 will have the same thing: "Fuel Surcharge".
The next column or field will be headed "Saturday delivery" and rows 96
through 130, for example, will also say: "Saturday delivery".

This may work better or easier in Excel for all I know.

Well... that's certainly NOT how relational databases are designed to work.
You should really have a normalized set of tables; if that term isn't
familiar, check out some of the references below.

You can run Append queries to selectively migrate the data from the jumbled
spreadsheet into your normalized tables, but to make effective use of Access,
you CANNOT keep changing the structure of your table based on the data that
you put into that table.

Jeff Conrad's resources page:
http://www.accessmvp.com/JConrad/accessjunkie/resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html

A free tutorial written by Crystal (MS Access MVP):
http://allenbrowne.com/casu-22.html

MVP Allen Browne's tutorials:
http://allenbrowne.com/links.html#Tutorials
 
Back
Top