智能客户端和离线ID号 [英] Smart Client and offline Id number

问题描述

Hello All，


我正在编写一个智能客户端应用程序，当然，应该在线下工作时使用大多数功能离线工作。程序

将有一个本地数据库，可以保存数据，直到便携式计算机上网并与主数据库同步。


我遇到的问题是，现场人员需要向客户提供一个案件

号码或参考号码，这些号码必须是唯一的所有

时间。同步后，本地和

集中式数据库中的此数字应相同。我正在考虑使用

以下格式ddmmyyOnSitePersonIDsequentialNumber或

OnSitePersonIDhhmmssddmmyy。但是，如果笔记本电脑上的RTC电池价格不好怎么办？这肯定会搞砸了。


有什么想法吗？这个问题有微软的标准吗？


我们的帮助表示赞赏。


艾哈迈德

Hello All,

I am programming a smart client application that should, of course,
work offline with most of the functionalities while online. The program
will have a local database that will keep the data till the portable
computer gets online and sync with the main database.

The issue I am having is the person on the field needs to give a case
number or a reference number to the client that must unique all the
time. This number should be the same in both the local and the
centralized database after syncing. I was thinking of using the
following format ddmmyyOnSitePersonIDsequentialNumber or
OnSitePersonIDhhmmssddmmyy. But, what if the RTC battery on the laptop
is bad? that will definitly screw things up.

Any ideas? Is there a Microsoft standart for this issue?

Your help is appreciated.

Ahmed

推荐答案

Ahmed，


您可以使用GUID。


Kerry Moorman

" Ahmed"写道：

Ahmed,

You might be able to use a GUID.

Kerry Moorman
"Ahmed" wrote:

Hello All，

我正在编写一个智能客户端应用程序，当然，它应该在大多数功能的同时离线工作线上。程序
将有一个本地数据库，可以保存数据，直到便携式计算机上线并与主数据库同步。

我遇到的问题是该字段需要给客户提供一个案例号码或参考号，这个号码必须是唯一的所有时间。同步后，本地和集中式数据库中的此数字应相同。我正在考虑使用以下格式ddmmyyOnSitePersonIDsequentialNumber或
OnSitePersonIDhhmmssddmmyy。但是，如果笔记本电脑上的RTC电池坏了怎么办？这肯定会搞砸了。

任何想法？是否有针对此问题的微软标准？

感谢您的帮助。

Ahmed

Hello All,

I am programming a smart client application that should, of course,
work offline with most of the functionalities while online. The program
will have a local database that will keep the data till the portable
computer gets online and sync with the main database.

The issue I am having is the person on the field needs to give a case
number or a reference number to the client that must unique all the
time. This number should be the same in both the local and the
centralized database after syncing. I was thinking of using the
following format ddmmyyOnSitePersonIDsequentialNumber or
OnSitePersonIDhhmmssddmmyy. But, what if the RTC battery on the laptop
is bad? that will definitly screw things up.

Any ideas? Is there a Microsoft standart for this issue?

Your help is appreciated.

Ahmed

使用GUID


希望这会有所帮助，

Brian Swanson


" Ahmed" <啊******* @ gmail.com>在消息新闻中写道：啊******* @ gmail.com：

Use a GUID

Hope this helps,
Brian Swanson

"Ahmed" <ah*******@gmail.com> wrote in message news:ah*******@gmail.com:

Hello All，

我正在编写一个智能客户端应用程序，当然应该
在线工作，具有大多数功能。程序
将有一个本地数据库，可以保存数据，直到便携式计算机上线并与主数据库同步。

我遇到的问题是该字段需要给客户提供一个案例号码或参考号，这个号码必须是唯一的所有时间。同步后，本地和集中式数据库中的此数字应相同。我正在考虑使用以下格式ddmmyyOnSitePersonIDsequentialNumber或
OnSitePersonIDhhmmssddmmyy。但是，如果笔记本电脑上的RTC电池坏了怎么办？这肯定会搞砸了。

任何想法？是否有针对此问题的微软标准？

感谢您的帮助。

Ahmed

Hello All,

I am programming a smart client application that should, of course,
work offline with most of the functionalities while online. The program
will have a local database that will keep the data till the portable
computer gets online and sync with the main database.

The issue I am having is the person on the field needs to give a case
number or a reference number to the client that must unique all the
time. This number should be the same in both the local and the
centralized database after syncing. I was thinking of using the
following format ddmmyyOnSitePersonIDsequentialNumber or
OnSitePersonIDhhmmssddmmyy. But, what if the RTC battery on the laptop
is bad? that will definitly screw things up.

Any ideas? Is there a Microsoft standart for this issue?

Your help is appreciated.

Ahmed

GUID'绝对是一个很好的规定方法，可以获得一个独特的

参考（或几乎是唯一的）。但是，从人的角度来看，它们并不总是可用的。很多时候，人们可能会使用b / b
序列增量值，而不是随机生成的值。


如果这是一个问题，您可能需要考虑使用自动编号字段

使用-1种子并减1，当您插入中央

数据库时，这些数字可以转换为唯一编号。 br />

IE

Me.DataSet11.Tables（0）.Columns（1）.AutoIncrementSee d = -1


Me.DataSet11.Tables（0）.Columns（1）.AutoIncrementSte p = -1

HTH


-

OHM（Terry Burns）

http://TrainingOn.net


" Ahmed" <啊******* @ gmail.com>在消息中写道

news：11 ********************* @ g14g2000cwa.googlegro ups.com ...

GUID''s are definately a well prescribed method of obtaining a unique
reference ( or virtually unique ). However, they are not allways useable
from a human perspective. There are many times that one might perfer a
sequenced incremental value rather than a randomly generated value.

If this is an issue, you may want to consider using an auto number field
with a -1 seed and decrement by 1, when you INSERT into the central
database, these numbers can be converted to a unique numbers.

I.E.
Me.DataSet11.Tables(0).Columns(1).AutoIncrementSee d = -1

Me.DataSet11.Tables(0).Columns(1).AutoIncrementSte p = -1
HTH

--
OHM ( Terry Burns )

http://TrainingOn.net

"Ahmed" <ah*******@gmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

大家好，

我正在编写一个智能客户端应用程序，当然，它应该在线工作时具有大部分功能。程序
将有一个本地数据库，可以保存数据，直到便携式计算机上线并与主数据库同步。

我遇到的问题是该字段需要给客户提供一个案例号码或参考号，这个号码必须是唯一的所有时间。同步后，本地和集中式数据库中的此数字应相同。我正在考虑使用以下格式ddmmyyOnSitePersonIDsequentialNumber或
OnSitePersonIDhhmmssddmmyy。但是，如果笔记本电脑上的RTC电池坏了怎么办？这肯定会搞砸了。

任何想法？是否有针对此问题的微软标准？

感谢您的帮助。

Ahmed

Hello All,

I am programming a smart client application that should, of course,
work offline with most of the functionalities while online. The program
will have a local database that will keep the data till the portable
computer gets online and sync with the main database.

The issue I am having is the person on the field needs to give a case
number or a reference number to the client that must unique all the
time. This number should be the same in both the local and the
centralized database after syncing. I was thinking of using the
following format ddmmyyOnSitePersonIDsequentialNumber or
OnSitePersonIDhhmmssddmmyy. But, what if the RTC battery on the laptop
is bad? that will definitly screw things up.

Any ideas? Is there a Microsoft standart for this issue?

Your help is appreciated.

Ahmed

这篇关于智能客户端和离线ID号的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！