how can i insert a row in MS access

  • Thread starter Thread starter Guest
  • Start date Start date
Swapna,

I suppose you are talking about an Append Query. There is some good
information on this topic in Access Help. If you need to automate the
process, you can use an OpenQuery action in a macro, or various ways of
doing it in a VBA procedure. If you neeed more help, please give more
details, maybe with examples, of what you are trying to do.
 
Hi Steve
Thanks for your reply.
Actually I got to insert a blank row in the table. Is there a possibility
to write a query for row insert or do i have to do it in Macros?

I have a table in Access and I need to insert a value in a particular
coloumn in the table, for which I need to insert the row

So how can I do that?
 
Swapna,

I don't understand. First of all, you say you need a blank row, and
then you say you need to insert a value in a field. As I mentioned
before, you can use an Append Query. It will help if you can give more
specific detail.
 
Hi Steve,

I tried with append query.

Actuually I have a main heading for example 5 and under the main heading i
have subheading´s for example 4111 , 4211, 4311, under these subheadings
there are hundereds of sales with id numbers 24111123, .........
24211456........ 24311123 respectively.
I have a row in my table with all the sub headings 4111, 4211, 4311
and other row in the table with all the sales ID´s 24111123, 24211456,
24311123 etc. I want in a format so that the main heading 5 is displayed and
then subheading 4111 is displayed and then all the sales Id´s under 5 and
4111 shoulñd be displayed in the same coloumn. one after the other.

I used a append query with a group function ..seperate rows are created for
subheadings but they are displayed at the top of the page, but in the
sequence.

Regards,
Swapna.
 
Swapna,

Thanks for the further explanation.

To be honest, the concept of "maoin heading" and "subheading" shouldn't
come into a discussion about a table. For two reasons. First of all,
no-one should ever see the table. That's not what tables are for.
Tables are for data storage, and in fact the way in which the data is
stored in tables makes it impossible to regulate the order in which
"rows" are displayed. Secondly, if you have groupings such as headings
and subheadings would imply, it really indicates that you have data
elements which have a "one-to-many" relationship with each other. In a
database, this means only one thing - you need two tables, with the data
on the "one" side of the relationship stored in one table, and the data
on the "many" side of the relationship stored in the other. In fact, on
the basis of the information you have provided so far, I would think you
need 3 tables. I am still not sure what your database is all about, but
perhaps a spreadsheet would be more applicable to your requirements?
 
Back
Top