[AccessD] Multiple Users Question - Replicated Database

Julie,
I am assuming that you are using SQL Server.

If you set the field as follows:
* Identity Yes - (NOT FOR REPLICATION )
* Increment (by1)

Then SQL Server will automatically assign a new unique number for every
record entered. SQL server keeps its own list of ID's and each subscriber
has its own range of IDs.

It is critical that you set the range sizes when you publish the database
as that is what SQL server uses to assign the ranges.

As you can imagne, you won't get a neat list of ID's in sequential order,
but you will eventually get to know the ranges and you will be able to
establish who created the record just by looking at ID.

Anita

On 9/14/07, Jim Lawrence <accessd at shaw.ca> wrote:
>
> Julie: Why not use GUID values as temp values. Their creation and nature
> almost guarantees self-contained uniqueness.
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Julie Reardon
> Sent: Thursday, September 13, 2007 10:45 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Multiple Users Question - Replicated Database
>
> Hi,
>
> I am kind of stuck on an issue and wondered if anyone has done this.
>
> My housing inspection software is being used locally and is working great.
>
> However, when I wrote the software, they were only using one tablet pc and
> replicating with the master copy on the server.
>
> Now they want to send multiple inspectors out there with tablet pc's.
>
> My problem is that when they create an inspection, I assign a unique
> inspection id.  That id follows the record through the inspection process,
> and then onto the Work Order that is created when there are repairs
> needed.
>
> If I have multiple inspectors with tablet pc's, I can't create the unique
> inspection id (automatically increments by one) when the inspection is
> created on the tablet pc, because I won't know which id each of the tablet
> pc's are using until the users synch with the copy on the server.
>
> Multiple inspectors means duplicate inspection id's.
>
> Is this making sense?
>
> I need a way to create a temporary inspection id that is unique and then
> when the inspector synchs with the server, a permanent id is assigned to
> the
> record.
>
> Anyone run into this?
>
> Is this the way to go about doing this?
>
> I'm not necessarily looking for code, just some opinions.
>
> Julie Reardon
> PRO-SOFT of NY, Inc.
> 44 Public Square, Suite 5
> Watertown, NY  13601
> Phone:  315.785.0319
> Fax:  315.785.0323
> NYS IT Contract#CMT026A
> NYS Certified Woman-Owned Business
> www.pro-soft.net
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>