how to increase the primary key value (ID) without set as Auto number in MS access

Question

0.00/5 (No votes)

See more:

HI
i created view for getting the maximum value of Stop-ID,So in StopNew() function i will add 1 to that Max Stop-ID

C#

public void StopNew()
       {

           this.MaxStopIDbindingSource.EndEdit();

           stopBindingSource.AddNew();
           this.MaxStopIDbindingSource.MoveFirst();
           ((DataRowView)this.stopBindingSource.Current).Row["nStopID"] = (int)((DataRowView)this.MaxStopIDbindingSource.Current).Row["nID"] + 1;

       }

but the max ID will not update in runtime, means view value will not updated in runtime.

Posted 4-Mar-11 23:17pm

sairam.bhat

Updated 4-Mar-11 23:25pm

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

_Maxxx_ · Answer 1 · 2011-03-15T17:21:00

I'm guessing a lot here, but the reason your view won't update at runtime is because you haven't updated your database yet - surely as soon as you commit the new record, your view will update?

If you need to be able to add multiple records, before committing your changes, then you'd have to keep a track of the id internally until you update.

This assumes this is a single-user database, of course.

For a multi-user database, if you need to know the value of a row;s ID without updating it first to the database, then you'd have to implement a new table, holding the next available (or last used) Id - and update that table every time you insert a record to your collection - that way every user gets the next available Id regardless.