A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Access 2007 with Vista



 
 
Thread Tools Display Modes
  #1  
Old May 26th, 2010, 07:02 AM posted to microsoft.public.access
royfarnol[_2_]
external usenet poster
 
Posts: 8
Default Access 2007 with Vista

Because of a power surge I lost one of my database records.

Is there anyway I can restore the missing auto number?

I would like to do so in order that several other database numbers remain
synchronised.

Thanks, Roy.

  #2  
Old May 26th, 2010, 01:13 PM posted to microsoft.public.access
Jon Lewis[_3_]
external usenet poster
 
Posts: 40
Default Access 2007 with Vista

This is a bad idea. There are a number of reasons why auto numbers may not
be contiguous and for that reason it's not advisable to use them for this
purpose. You can try to generate your own sequential series of numbers but
even that probably wouldn't be completely fool proof.

Post details of the synchronisation you need as there's probably another
solution.

HTH

Jon





"royfarnol" wrote in message
...
Because of a power surge I lost one of my database records.

Is there anyway I can restore the missing auto number?

I would like to do so in order that several other database numbers remain
synchronised.

Thanks, Roy.



  #3  
Old May 27th, 2010, 02:29 AM posted to microsoft.public.access
royfarnol[_2_]
external usenet poster
 
Posts: 8
Default Access 2007 with Vista

It probably is a bad idea but it has been done and it involves other
people's databases.

The Access program I run produces an item number, by way of the autonumber
function, which is then notified to several other people as a master item
number. After that each procesesses the information in their own way. When
results (or sometimes lack of results) are finalised (or exhuasted) the
report comes back under the master number.

I would rather not have to begin again as it were but reintroduce the number
that was obliterated by the power surge. I know one could issue a number of
one's own but human error then creeps in, which is why the autonumber
function was picked in the first place.

But maybe you have a better idea or a workaround solution?

Thanks, Roy.


"Jon Lewis" wrote in message
...
This is a bad idea. There are a number of reasons why auto numbers may
not be contiguous and for that reason it's not advisable to use them for
this purpose. You can try to generate your own sequential series of
numbers but even that probably wouldn't be completely fool proof.

Post details of the synchronisation you need as there's probably another
solution.

HTH

Jon





"royfarnol" wrote in message
...
Because of a power surge I lost one of my database records.

Is there anyway I can restore the missing auto number?

I would like to do so in order that several other database numbers remain
synchronised.

Thanks, Roy.




  #4  
Old May 27th, 2010, 05:02 PM posted to microsoft.public.access
KenSheridan via AccessMonster.com
external usenet poster
 
Posts: 1,610
Default Access 2007 with Vista

You can insert a row into the table, with a specific value for the autonumber
column by means of an 'append' query, e.g.

INSERT INTO [YourTable] ([ItemNumber], [ItemText])
VALUES(42, "Widget");

But relying on an auto number to give an uninterrupted sequence is very risky.
Its far better to automatically compute the number when a row is inserted.
Roger Carlson has simple solutions, for both single-user and multi-user
environments at:

http://www.rogersaccesslibrary.com/forum/topic395.html

and there is a more complex one of mine for use in a multi-user environment,
which also allows for the next number to be used to be 'seeded' at:

http://community.netscape.com/n/pfx/...g=ws-msdevapps


Ken Sheridan
Stafford, England

royfarnol wrote:
It probably is a bad idea but it has been done and it involves other
people's databases.

The Access program I run produces an item number, by way of the autonumber
function, which is then notified to several other people as a master item
number. After that each procesesses the information in their own way. When
results (or sometimes lack of results) are finalised (or exhuasted) the
report comes back under the master number.

I would rather not have to begin again as it were but reintroduce the number
that was obliterated by the power surge. I know one could issue a number of
one's own but human error then creeps in, which is why the autonumber
function was picked in the first place.

But maybe you have a better idea or a workaround solution?

Thanks, Roy.

This is a bad idea. There are a number of reasons why auto numbers may
not be contiguous and for that reason it's not advisable to use them for

[quoted text clipped - 16 lines]

Thanks, Roy.


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/201005/1

  #5  
Old May 28th, 2010, 06:49 AM posted to microsoft.public.access
royfarnol[_2_]
external usenet poster
 
Posts: 8
Default Access 2007 with Vista

Thankyou Mr. Sherdian. I'll look into those links you gave for a better way.

"KenSheridan via AccessMonster.com" u51882@uwe wrote in message
news:a8a302da457c1@uwe...
You can insert a row into the table, with a specific value for the
autonumber
column by means of an 'append' query, e.g.

INSERT INTO [YourTable] ([ItemNumber], [ItemText])
VALUES(42, "Widget");

But relying on an auto number to give an uninterrupted sequence is very
risky.
Its far better to automatically compute the number when a row is inserted.
Roger Carlson has simple solutions, for both single-user and multi-user
environments at:

http://www.rogersaccesslibrary.com/forum/topic395.html

and there is a more complex one of mine for use in a multi-user
environment,
which also allows for the next number to be used to be 'seeded' at:

http://community.netscape.com/n/pfx/...g=ws-msdevapps


Ken Sheridan
Stafford, England

royfarnol wrote:
It probably is a bad idea but it has been done and it involves other
people's databases.

The Access program I run produces an item number, by way of the autonumber
function, which is then notified to several other people as a master item
number. After that each procesesses the information in their own way. When
results (or sometimes lack of results) are finalised (or exhuasted) the
report comes back under the master number.

I would rather not have to begin again as it were but reintroduce the
number
that was obliterated by the power surge. I know one could issue a number
of
one's own but human error then creeps in, which is why the autonumber
function was picked in the first place.

But maybe you have a better idea or a workaround solution?

Thanks, Roy.

This is a bad idea. There are a number of reasons why auto numbers may
not be contiguous and for that reason it's not advisable to use them for

[quoted text clipped - 16 lines]

Thanks, Roy.


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/201005/1


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 12:27 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.