Reconfiguration incident to enabling an application access to setup information therefor

• US 20020026572A1
• Filed: 08/31/2001
• Published: 02/28/2002
• Est. Priority Date: 08/31/2000
• Status: Abandoned Application

• Current Assignee: Docubase Limited
• Original Assignee: Docubase Limited
• Inventors: Joory, Rafael
• Application Number:
  US09/942,923
• Publication Number:
  US 20020026572A1
• Time in Patent Office: Days
• US Class Current: 713/100
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

The setup data from a source application or computer may be accessed and used to supplant the setup data from a destination application or computer, and the supplanted setup data may be preserved for reinstatement or future access. The destination computer may be reconfigured to access setup data for one of its destination software applications. For instance, reconfiguration may include identifying first setup data accessible to at least one but less than all destination software applications performed by the destination computer, preserving the first setup data, and enabling use by less than all of the destination software applications of second setup data rather than the first setup data.

Claims

1. A method for reconfiguring a destination computer to access setup data for at least one destination software application performed by the destination computer, the method comprising:

identifying first setup data accessible to at least one but less than all destination software applications performed by the destination computer;

preserving the first setup data; and

enabling use by less than all of the destination software applications of second setup data rather than the first setup data.

2. The method of claim 1, wherein preserving the first setup data includes temporarily disabling use of the first setup data by renaming the first setup data from a first name to a second name, and

enabling use of the second setup data comprises making the second setup data accessible under the first name to the destination software application performed by the destination computer.

3. The method of claim 1, further comprising making the first setup data inaccessible to the destination software applications after preserving the first setup data.

4. The method of claim 1, wherein identifying the first setup data accessible to the destination software application comprises identifying the first setup data from among data stored on the destination computer and accessible to the destination software application performed by the destination computer.

5. The method of claim 4, wherein:

preserving the first setup data comprises accessing the first setup data from a first location on the destination computer and storing the first setup data to a second location on the destination computer, and

enabling use of the second setup data comprises storing the second setup data in the first location on the destination computer.

6. The method of claim 5, wherein enabling use of the second setup data further comprises deleting the first setup data from the first location after storing the first setup data to the second location.

7. The method of claim 4, wherein:

preserving the first setup data comprises accessing the first setup data on the destination computer and storing the first setup data to a data store that is remote from the destination computer, and

enabling use of the second setup data comprises storing the second setup data on the destination computer.

8. The method of claim 7, wherein enabling use of the second setup data further comprises deleting the first setup data from the destination computer after storing the first setup data to the data store that is remote from the destination computer.

9. The method of claim 4, wherein the destination software program supports multiple identities, and wherein enabling use of the second setup data comprises:

programmatically creating a secondary identity in the destination software application,

associating the second setup data with the secondary identity, and

referencing the second setup data associated with the secondary identity rather than the first setup data.

10. The method of claim 9, wherein associating the second setup data with the secondary identity comprises using pointers to enable access to the second setup data.

11. The method of claim 9, wherein associating the second setup data with the secondary identity comprises copying the second setup data to memory locations corresponding to data for the secondary identity.

12. The method of claim 9, wherein associating the second setup data with the secondary identity comprises moving the second setup data to memory locations corresponding to data for the secondary identity.

13. The method of claim 4, wherein enabling includes programmatically replacing the first setup data associated with a software application with the second setup data to enable a second identity for a software application designed to support a single identity.

14. The method of claim 1, wherein identifying the first setup data comprises identifying data stored on a computer accessible to the destination computer and accessible to the destination software application performed by the destination computer.

15. The method of claim 14, wherein preserving the first setup data includes saving the first setup data at a computer accessible to the destination computer.

16. The method of claim 14, wherein enabling use of the second setup data includes enabling access to second setup data stored on a computer accessible the destination computer.

17. The method of claim 1, wherein the first setup data includes first customized configuration settings data for the destination software application performed by the destination computer.

18. The method of claim 17, wherein the second setup data includes second customized configuration settings data generated from one or more software applications other than the destination software application performed by the destination computer, the second setup data being useful to the destination software application performed by the destination computer.

19. The method of claim 1, wherein the first setup data includes data previously established at a computer other than the destination computer.

20. The method of claim 1, wherein the first setup data includes data previously established by a software application other than the destination software application.

21. The method of claim 1, wherein the second setup data corresponds to a computer user that has not previously used the destination computer.

22. The method of claim 21, wherein the second setup data corresponds to a computer user that has not previously used the destination software application on the destination computer.

23. The method of claim 1, further comprising:

identifying first end-purpose data accessible to at least one but less than all destination software applications performed by the destination computer;

preserving the first end-purpose data; and

enabling use by less than all of the destination software applications of second end-purpose data rather than the first setup data.

25. The method of claim 24, wherein restoring the original settings includes deleting the other settings and enabling the original settings that are preserved.

26. The method of claim 25, wherein restoring the original settings for the software application includes returning the software application to a configuration preceding the preserving.

27. The method of claim 25, wherein the software application is a software application supporting multiple identities and the original settings and the other settings are each associated with a single identity.

28. The method of claim 27, wherein the identities correspond to user profiles.

29. The method of claim 27, wherein enabling other settings includes programmatically creating a secondary identity in the software application supporting multiple identities, and wherein restoring the original settings for the software application includes deleting the secondary identity.

24. A method for manipulating customized configuration settings data on a computer, comprising:

preserving original settings for at least one but less than all software application performed by a computer;

enabling settings that differ from the original settings for less than all of the software applications performed by the computer for purposes of reconfiguring the software application performed by the computer, and

restoring the original settings for the software application.

30. A computer program, stored on a computer readable medium, for processing data with a computer system to reconfigure a destination computer to access setup data for at least one destination software application performed by the destination computer, the computer program comprising:

identifying first setup data accessible to at least one but less than all destination software applications performed by the destination computer;

preserving the first setup data; and

enabling use by less than all of the destination software applications of second setup data rather than the first setup data.

31. The computer program of claim 30, wherein preserving the first setup data includes temporarily disabling use of the first setup data by renaming the first setup data from a first name to a second name, and

enabling use of the second setup data comprises making the second setup data accessible under the first name to the destination software application performed by the destination computer.

32. The computer program of claim 30, further comprising making the first setup data inaccessible to the destination software applications after preserving the first setup data.

33. The computer program of claim 30, wherein identifying the first setup data accessible to the destination software application comprises identifying the first setup data from among data stored on the destination computer and accessible to the destination software application performed by the destination computer.

34. The computer program of claim 33, wherein:

preserving the first setup data comprises accessing the first setup data from a first location on the destination computer and storing the first setup data to a second location on the destination computer, and

enabling use of the second setup data comprises storing the second setup data in the first location on the destination computer.

35. The computer program of claim 34, wherein enabling use of the second setup data further comprises deleting the first setup data from the first location after storing the first setup data to the second location.

36. The computer program of claim 33, wherein:

preserving the first setup data comprises accessing the first setup data on the destination computer and storing the first setup data to a data store that is remote from the destination computer, and

enabling use of the second setup data comprises storing the second setup data on the destination computer.

37. The computer program of claim 36, wherein enabling use of the second setup data further comprises deleting the first setup data from the destination computer after storing the first setup data to the data store that is remote from the destination computer.

38. The computer program of claim 33, wherein the destination software program supports multiple identities, and wherein enabling use of the second setup data comprises:

programmatically creating a secondary identity in the destination software application,

associating the second setup data with the secondary identity, and

referencing the second setup data associated with the secondary identity rather than the first setup data.

39. The computer program of claim 38, wherein associating the second setup data with the secondary identity comprises using pointers to enable access to the second setup data.

40. The computer program of claim 38, wherein associating the second setup data with the secondary identity comprises copying the second setup data to memory locations corresponding to data for the secondary identity.

41. The computer program of claim 38, wherein associating the second setup data with the secondary identity comprises moving the second setup data to memory locations corresponding to data for the secondary identity.

42. The computer program of claim 33, wherein enabling includes programmatically replacing the first setup data associated with a software application with the second setup data to enable a second identity for a software application designed to support a single identity.

43. The computer program of claim 30, wherein identifying the first setup data comprises identifying data stored on a computer accessible to the destination computer and accessible to the destination software application performed by the destination computer.

44. The computer program of claim 43, wherein preserving the first setup data includes saving the first setup data at a computer accessible to the destination computer.

45. The computer program of claim 43, wherein enabling use of the second setup data includes enabling access to second setup data stored on a computer accessible the destination computer.

46. The computer program of claim 30, wherein the first setup data includes first customized configuration settings data for the destination software application performed by the destination computer.

47. The computer program of claim 46, wherein the second setup data includes second customized configuration settings data generated from one or more software applications other than the destination software application performed by the destination computer, the second setup data being useful to the destination software application performed by the destination computer.

48. The computer program of claim 30, wherein the first setup data includes data previously established at a computer other than the destination computer.

49. The computer program of claim 30, wherein the first setup data includes data previously established by a software application other than the destination software application.

50. The computer program of claim 30, wherein the second setup data corresponds to a computer user that has not previously used the destination computer.

51. The computer program of claim 50, wherein the second setup data corresponds to a computer user that has not previously used the destination software application on the destination computer.

52. The computer program of claim 30, further comprising:

identifying first end-purpose data accessible to at least one but less than all destination software applications performed by the destination computer;

preserving the first end-purpose data; and

enabling use by less than all of the destination software applications of second end-purpose data rather than the first setup data.

53. A computer program for manipulating customized configuration settings data on a computer, comprising:

preserving original settings for at least one but less than all software application performed by a computer;

enabling settings that differ from the original settings for less than all of the software applications performed by the computer for purposes of reconfiguring the software application performed by the computer, and

restoring the original settings for the software application.

54. The computer program of claim 53, wherein restoring the original settings includes deleting the other settings and enabling the original settings that are preserved.

55. The computer program of claim 54, wherein restoring the original settings for the software application includes returning the software application to a configuration preceding the preserving.

56. The computer program of claim 54, wherein the software application is a software application supporting multiple identities and the original settings and the other settings are each associated with a single identity.

57. The computer program of claim 56, wherein the identities correspond to user profiles.

58. The computer program of claim 56, wherein enabling other settings includes programmatically creating a secondary identity in the software application supporting multiple identities, and wherein restoring the original settings for the software application includes deleting the secondary identity.