I need to change the creation date of an nsf.
How do i proceed with it???
i searched and found out that database.Created is an >> read-only value and cannot be changed.
http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.designer.domino.main.doc%2FH_CREATED_PROPERTY_DB.html
Is there any way by which i can do so????
Thanks In Advance.
If you change the Database to a template by changing the file extension to .ntf, and then create a new database based on that template, that will change the created date
UPDATE:
You can also accomplish this using the "Database > New Copy" option (or Application > New Copy in version 8.x)
If you create an operating system copy of the file, the Notes creation date should remain the same. Otherwise, you can't have a creation date earlier than today.
As I don't think this is in general a good idea I didn't test this, but it might work :
Shutdown the server.
then make a OS copy of the NSF you want to manipulate to your PC.
Change date/time of your local PC.
Start Notes, make a copy.
Copy this new NSF back to your server (OS copy).
Related
It seems like Sticky Notes are no longer saved in %AppData%\Microsoft\Sticky Notes\
I even did a search for *.SNT with no results.
It seems like Microsoft have changed the way Windows handles Notes. Anyone know where the notes are saved now and how to backup/restore them?
Use this document to transfer Sticky Notes data file StickyNotes.snt to the new format
http://www.winhelponline.com/blog/recover-backup-sticky-notes-data-file-windows-10/
Restore:
%LocalAppData%\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\LocalState
Close Sticky Notes
Create a new folder named Legacy
Under the Legacy folder, copy your
existing StickyNotes.snt, and rename it to ThresholdNotes.snt
Start the Sticky Notes app. It reads the legacy .snt file and
transfers the content to the database file automatically.
Backup
just backup following file.
%LocalAppData%\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\LocalState\plum.sqlite
It appears Microsoft now stores them in a SQLite database file called plum.sqlite located here:
C:\Users\%username%\AppData\Local\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\LocalState\plum.sqlite
It depends on the version of Windows 10 you're using. Starting with Windows 10 Anniversary Update version 1607, Sticky Notes is storing its data in the following directory:
%UserProfile%\AppData\Local\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe
If your Windows 10 has an older version, it is storing the date in the following directory:
%UserProfile%\AppData\Roaming\Microsoft\StickyNotes\StickyNotes.snt
Here what i found. C:\Users\User\AppData\Local\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\TempState
There is snapshot of your sticky note in .png format. Open it and create your new note.
Sticky notes in Windows 10 are stored here:
C:\Users\"Username"\Appdata\Roaming\Microsoft\Sticky Notes
If you want to restore your sticky notes from earlier versions of windwos, just copy the .snt file and place it in the above location.
N.B: Replace only if you don't have any new notes in Windows 10!
If at all you can't find .snt folder and above mentioned answers don't work for you. you can simply take plum.sqlite file and read it online or sqlite editor.
for online you can refer to http://inloop.github.io/sqlite-viewer/ link and browse the url as C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\LocalState
and pick sql lite file and execute it. Post executing select Note and you will find all rows corresponding to each sticky notes you have lost. Select the Text column and copy content, you will find all your data there.
ENJOY !!!!
In windows 10 you can recover in this way, there is no .snt file
Start Run
Go to this %LocalAppData%\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe
Copy this folder Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe
Replace it with new Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe
Check your sticky notes now, you will get all your data
It worked for me when HDD with win8.1 crashed and my new HDD has win10.
Important to know
- Create Legacy folder mentioned in this link.
- Remember to rename the StickyNotes.snt to ThresholdNotes.snt.
- Restart the app
Find details here
https://www.reddit.com/r/Windows10/comments/4wxfds/transfermigrate_sticky_notes_to_new_anniversary/
I am trying to create a batch file as icon on desktop, that would open a specific excel file, create a macro in it and copy code from a specific txt file into it.
The reason i need this, is that the file is located on a server and the ending .xlm cannot be cahanged (should not) so i cannot save it as a macro enabled file (to store a macro in it )
Could annyone with better understanding please explain to me how to create the said code ?
Thanks in advance!
In theory it's possible by using the VBE object (https://msdn.microsoft.com/en-us/library/aa443984%28v=vs.60%29.aspx). But that's not activated by default so you can not ensure that each user is able to do that.
Better find other solutions for that problem. Can you upload .XLSB for example? Or do you have another kind of server available - for example a database server - you can use for storing the file? We use this method here for deploying our updates on AddIns and report templates for example.
I'm working on an app and need to make an update to the xcdatamodel file.
So I created a new file:
I have model.xcdatamodel
and now I have model2.xcdatamodel
However, it looks like the app is still using model.xcdatamodel. How can I change that to point to model2.xcdatamodel?
I see that next to model.xcdatamodel, there is a "green check icon".
Thank you,
Tee
Ah I got it. Just need to select model.xcdatamodeld (i.e the parent of all xcdatamodel files) and change the "Versioned core data model" to the one you want to use.
I've got this one thing I'm not really sure where to begin with. In our SharePoint 2007 solution, we've got this project room where each employee has their own folders with their resumé etc. And we want this information to be distributed to their MySite.
I've noticed that I can basically copy the files from one are to the other. But the files in MySite are connected to the corresponding user based on properties of some sort. But they are not regular file properties is seems. When I open all of the files in the MySite files collection, I can see categories such as Title and Name. If I copy a file in there, these properties are blank. And if I manually assign a username to the Name property, the file automatically appears in the correct user's MySite.
Probably horribly explained.. But, is it possible to program this somehow? I would like a nightly or weekly schedule that basically copies the content and assigns the username and title to the correct fields. I can pick up both the title and the username based on the folder names. This I can probably solve later. It's just where to begin that's bothering me. Do I use SharePoint designer? Can I user VB code? Do I have to code at all? I've never developed a thing for SharePoint before. And no, I do not want to be redirected to a basic "Getting started with developing for Sharepoint" site.. Just a simple answer really, on where to begin.
Simple answer: Yes you can use VB. Create Timerjobs.
TimerJobs you can set to start on specific weekdays, specific hours etc. and they do exactly whatever you program them to do.
We have a lot of VBA code in spreadsheets and a lot of time people save them to local drives. When we want to upgrade the spreadsheets we push a new version out to a shared drive but dont have any way of enforcing that people dont use the old versions of the spreadsheets.
Is there some best practice here to deploy vba spreadsheets so if someone loads an old version it wont open or will ask you to upgrade. It seems like this must be an issue for any custom solution so i would have through MS would have some solution here.
Does microsoft have a standard versioning / deployment solution for this or do i need to come up with some home grown solution (spreadsheet pings a database on startup to check version)
If its just the VBA code you want to be able to upgrade one solution is to separate all the code into an XLA that sits on an accessible server.
then the users Excel has an addin loader that gets the latest version from the server, or you could embed the loader in the workbook.
There is a working example reversioning Addin Loader available at
http://www.decisionmodels.com/downloads.htm
Though I've not done this. I've see people do something similar where they store the code in dlls in the database, and then verify that the local ones are the same on start up.
Add a custom property to the workbook, such as a GUID, Integer, Date, or whatever you need. On startup, check the value and determine if VBA should continue or whatever implementation you decide. Usually, I open the "shared" latest version of the document and inspect its custom property. If user is not using latest version, display a message prompting the user to get the latest version. This is usually good enough. I have done this for years with great success for Access, Word, and Excel VBA.
One real problem is people who ignore the prompt to update. They will do this because they fear losing data, bugs in latest version, and so on. You need to address their concerns and not try to "lock" them in to your "solution" to this problem. I strongly recommend you always provid a means of "importing/upgrading" data to latest version of workbook.
Fairly simple to implement. If you address the above mentioned problem effectively, people will start to trust the "prompt" and you will find this is a really simple and effective solution.
If you workbook is tied to a database, it gets a little more complicated. Generally, you do not allow the user to maintain the data outside of the database. When they want to modify the data, you generate the workbook for them. After they are done modifying data, you import the data. (The workbook is saved for "backup" purposes or the user can maintain a copy of the workbook for reference or an archive.) This has the advantage of eliminating the need to maintain document version since the document is "virtual".
Define a current version property. Use whatever way for that, like a constant in VBA.
Find a standard way to access the latest version. It could be on a shared drive always on the same path, or whatever other means you have.
If current version number < latest version number then:
Ask to upgrade
Show the upgrade procedure
Possibly do some locking on normal VBA operations until the upgrade is done
An easy solution would be:
Store a version number somwhere in the workbook (on a hidden sheet for example so that it will not get removed accidentally) or as a variable.
Store a text file with the latest version number on your share
Include a macro which automatically reads the latest-version-textfile and compares the version number to the one in the currently running workbook. If its too old just show a message-box (telling the user to update) and close the workbook.
I'm using a similar approach and it works fine.