Inserting or moving a record to a different position in the table 2

[Patentinv]

Hi,
With a table in open view can a record be moved to a different position, i'm using access 2003. Also is there any way to sort besides ascending or descending?
I've got a lot of tables to make and if I forget a single column/field and have to add it later (like I have done all ready numerious times) I'm almost having to recreate the table again in order to have the field fit in the correct spot in the table. These tables are bound to combo boxes so its important every thing is grouped for easy choosing.

Thanks--All help will be very appreciated

 

[Lilliabeth]

Are you trying to move columns or move records?

If you are trying to control the order of records, consider adding a sequence field that you can enter integers into and then sort by this field.

 

[Patentinv]

Hi Lilliabeth,
I mean records, sorry. I thought maybe there would be an easier way, I'll just pay more attention and try not to forget any records.

Thanks-- for your suggextion.

 

[SkipVought]

Hi,

The position of Rows in a table is absolutely irrelevant.

When you query (report), you can order rows. You need to understand basic database principles

http://www.alphabetcitydataworks.com/FundamentalsOfRelationalDatabaseDesign.doc

The Normal Forms are based on relations rather than tables. A relation is a special type of table that has the following attributes:

1. They describe one entity.
2. They have no duplicate rows; hence there is always a primary key.
3. The columns are unordered.
4. The rows are unordered.

Skip,

_{[red]A palindrome gone wrong?[/red]
A man, a plan, a ROOT canal...
PULLEMALL!}

 

[Lilliabeth]

Skip, I couldn't agree more. Trying to enter records in a particular order is, to be blunt, very foolish.

I roger that sequence is not generally controlled by such means when it can be accomplished by a particular sort, however complex. But when sequence is arbitrary and important, such as for recipe mixing instructions, it must be controlled with a sequence field. If you have another idea, I'd love to hear it.

She said she needed to sort other than alphabetically, which makes the sort arbitrary. And because she has put a fair amount of effort into this, I assume the sequence is important. Hence, I advised adding a sequence field.

 

[Patentinv]

Hi SkipVought,
Yes I'am a beginner and I could not agree more, I'll certainly read up on th basics of ralationships and database design.

Maybe if I keep running into problems I'll have to resort to adding a sequence field.

Thanks--For your help.

 

[MajP]

PatentInv,
What you are doing sounds like you are building what are commonly referred to as Look Up tables or Reference tables. You will populate these tables and then use values from them to place into your data tables. In these cases always put an integer (or single) field in these types of tables called:
intSortOrder
If I do not use it, then I get rid of it. But most times I find a need to present this data in some non alphabetic way.
example

recorsds as entered

intSortOrder Description
1            Agree
2            Slightly agree
5            disagree
3            neutral
4            slightly disagree

Sorted on intSortOrder

1            Agree
2            Slightly agree
3            neutral
4            slightly disagree
5            disagree