IT Employment

Pls post the query.. maybe its a query prob....

I'm sure many here would be happy to help. We'll need the query, of course, to give anything specific (open in Design View, then go to View and choose "SQL View", copy, and paste into your own "reply" to your original question). But lacking that, I would encourage you to look for the way your system handles nulls. I've often been bitten by this, and find that I can write workaround query columns that suffice, like "TotalPmts: iif([Pmt1]=null,0,[Pmt1])+iif([Pmt2]=null,0,[Pmt2])+iif([Pmt3]=null,0,[Pmt3])". (I also recognize that this is probably doing it the sloppy or hard way, and someone with proper training could do an elegant job which is currently beyond me - hey, for self-taught, I'm pleased at my progress... perhaps someone could suggest a way that both amalijohn and I could profit from.)

The primary key assigns 22 because at one time or another in the testing, probably, you had 21 dummy lines that you deleted. The system remembers not to reassign those numbers and starts at 22.

You might also find the answer already waiting for you at www.experts-exchange.com. I participate in both groups - this one for a better understanding of office politics, and experts-exchange for specific technical questions.

Try this,

First, Open your table in design view, click on a numeric field, then double-check the field properties at the bottom. Make sure that there are no 6 or -6 value in all fields (do this step in all numeric fields).

Second, click on the primary key, make sure the NEW VALUES in General tab (at the bottom--Field Properties) says INCREMENT.

Goodluck.