I am using an accounting software named BusyWin for almost an year. I set up an admin password in the software. It created two password protected mdb files for storing records. Somehow my database got corrupted(the busywin is giving the error saying it is corrupted; access is just asking for the password), now I am unable to open the same with the busywin software. I also tried to open the mdb file using access but it looks like the password is not same as the one used in BusyWin.
I contacted the developers of BusyWin and they agreed to repair the file for some amount but they are asking me to send the mdb files to their office. The data I have is highly confidential and I cant trust anyone with that.
Please let me know if there is any way to either recover the file or to derive the password from the admin password I have.
Here is the solution, i use this long many year ago. Please follow the some steps:-
First of all backup of your mdb file to other location.
Now click on your backuped mdb file.
It asking for password, enter the password : ILoveMyINDIA
File open in MS-Access check the table for USERS & ADMIN
Now close the file without saving.
reply me: moryasanjay#gmail.com
Related
I am currently developing an Access-Database for my company. In order to prevent Users from unauthorized changing of the VBA-code I have encrypted my Back- and Frontend .accdb file. I continued by compiling my frontend to an .accde file, which is not currently not password-protected.
Is it possible to read the used password for Front- and Backend using the .accde file only?
The .accde isn't connected to the .accdb it was created from, so if the .accde isn't encrypted, I don't see how it would contain the .accdb password.
But the backend password is most probably readable, by opening the .accde from another database and browsing the tabledefs and their properties (connection string).
To prevent this, you must encrypt the .accde too, and launch it from a seperate application, so you don't have to provide the password to the users.
Here is an approach: https://stackoverflow.com/a/46196870/3820271
Set pssword for .mdf file in sqlserver.
When you attach a file to someone, I want to ask him the password. In both cases, windows authorization and sqlserver authorization.
You can encrypt a database using tde which will prevent anyone from attaching an mdf file to another instance. It uses certificates and as usual simple talk has a great article as to how to use it and how it works. If someone has the correct certificate they can attach it.
I am trying to import data from an Access 2003 mdb database using OpenDataSource with the ACE OLEDB driver. I'm getting this error:
Description: OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)" returned message "Cannot start your application. The workgroup information file is missing or opened exclusively by another user.".
I have no idea what it's talking about, and my internet searches have not helped. They all refer to linked servers, and anything I've tried has done nothing to fix the problem. What does this error mean, and what do I need to do to fix it?
The sproc which does the importing is called from an SSIS package, which goes through a table of file locations and calls the sproc for each of them. I just discovered that the package ran for about half an hour, getting about 80 files imported, before it began throwing this error. I have as yet been unable to find any difference between the files that worked and the ones that didn't.
From Understanding the role of workgroup information files in Access security:
The workgroup information file is a required component when you use a
Microsoft Access database (MDB). This file is required for both a
run-time installation and a full installation of Microsoft Access.
This file is an important component of Microsoft Access security.
If you develop database applications, it is important that you have a
good understanding of the workgroup information file. It is a good
idea to reserve the last phase of the development process for applying
security in Access. Until then, you can develop the database
application in an unsecured database.
A workgroup is a group of users who share data in a multiuser
environment. When security is implemented on a database, the user and
group accounts are recorded in the workgroup information file. User
passwords are also stored in the workgroup information file.
IMPORTANT: If you establish Access security in a database, Microsoft
recommends that you store a backup copy of the workgroup information
file in a safe location. If the file is lost or damaged, the only way
to recover the workgroup information file quickly is to restore the
file from a backup copy. If you do not have a backup copy, you must
re-create the User and Group Accounts with the same Personal IDs that
were originally assigned. If the new workgroup information file is not
created exactly as the original file, you will not be able to open the
database with the workgroup file.
Access uses the workgroup information file even when the database has
not been secured. The default Admin user account, which is stored in
the workgroup information file, is used to open all unsecured
databases. If you assign a password to the Admin user, you will
receive a logon prompt when you reopen the database.
The Access database that SQL Server is trying to access is being used by another user. Go to the folder where the database is stored. With Access 2003, the database file itself will end in 'mdb'. If there is a file with the same name but ending in 'idb', it signals that there is a user currently using the 'mdb' file. Have the user exit the database and then run your package. If you can't find the user using the file, make a copy of the file in another folder and edit your SSIS package to reflect the change.
Im building an app which uses Sqlite DB.
Users can enter their information into the db and retrieve them.
However, I want them to be able to backup the sqlite db.
What I did was putting the sqlite db in the documents folder, so they could retrieve it out using iTunes.
For example if the ipad is faulty, i want them to be able to transfer the sqlite db to another ipad.
The problem now is, I dont want them to know the information inside the db, should say the db structure.
So how can I build a db that is able to read by my application only? and when they use sqlite browser to open, they wont be able to see anything.
I'm looking for something simple. Possible to have the db to prompt a password before opening it?
Here is the link to your answer, SQLCipher is the best thing, which will encrypt the whole database and if any one get the database from the iOS device, any how , still it will prompt for a password otherwise is will not allow user to see the same. even with Command prompt the user will not be able to see the database.
Hope this will be usefull....
I am attempting to run a Timed Subscription in SSRS 2008 and have the results save out to a file share. The subscription runs great when I have it email it's results but fails with this error when I try to save to a file share:
Failure writing file \ServerName\ShareName\Test.csv : Could not find file '\ServerName\ShareName\Test.csv'.
So Far, this is what I have unsuccessfully tried/confirmed
The subscription runs under my NT context and I've confirmed I have rights to create files in the share
I didn't expect it to matter but I created an empty text file name test.csv in the share. This made no difference
There are quite a few references online regarding write failures but non relate to "Could not find file".
I am the owner of the subject and the report
Emailing the report works fine
I tried leaving the file name blank in the subscription so SSRS would create the file name based on the RDL name (idea based on comments in BOL) but this is now a required field.
This is extremely frustrating. Has anyone had problems with this before? This seems like a slam dunk simple thing to do.
Are you qualifying your server name with a double backslash?
e.g.
\\ServerName
Not
\ServerName
Do you have the "Use as Windows credentials when connecting to the data source" box checked in Properties/Data Sources for that specific report?