Database

dan!sh 31-Aug-10 1:03

dan!sh

31-Aug-10 1:03

Password protection?

All Time Programming31-Aug-10 3:15

All Time Programming

31-Aug-10 3:15

That is for sure. But their are also some who can crack the password. Thinking for protection from that prospect, I think should have somethign more solid also maybe along with password protection.

Thanks & Regards,

Dave Kreskowiak31-Aug-10 4:27

Dave Kreskowiak

31-Aug-10 4:27

Then you can't use an Access database. You'd have to use SQL Server for better protection.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

dan!sh 31-Aug-10 5:05

dan!sh

31-Aug-10 5:05

You should keep the password encrypted in the configuration file for increased security. Still, as Dave said, if you have sensitive data in it, then go for SQL. You can make use of SQL express edition since that is free hence will not charge you more money. Smile | :)

Md. Marufuzzaman31-Aug-10 1:38

Md. Marufuzzaman

31-Aug-10 1:38

Try the link below:
http://office.microsoft.com/en-us/access-help/encrypt-a-database-by-using-a-database-password-HA010096299.aspx[^]

Thanks
Md. Marufuzzaman

I will not say I have failed 1000 times; I will say that I have discovered 1000 ways that can cause failure – Thomas Edison.

All Time Programming31-Aug-10 3:13

All Time Programming

31-Aug-10 3:13

I had read about encrypting the DB, but for usage as a backend will have to decrypt each time I use the DB via application and the applicatio nwill be running almost the whole day. Encrypting & Decrypting huge db often is not a good idea according to me.

What do you think ?

Thanks & Regards,

Md. Marufuzzaman31-Aug-10 6:08

Md. Marufuzzaman

31-Aug-10 6:08

As per your clarification, I think you are right.

Thanks
Md. Marufuzzaman

I will not say I have failed 1000 times; I will say that I have discovered 1000 ways that can cause failure – Thomas Edison.

Corporal Agarn31-Aug-10 3:15

Corporal Agarn

31-Aug-10 3:15

Access is a bad production database because it is so open. Can you use SQL Express or some other for the back end?

Note when you use a password on Access you open a new set of problems.

SimulationofSai31-Aug-10 6:23

SimulationofSai

31-Aug-10 6:23

If it's not possible to use SQL Server as others have suggested, you can always encrypt data that's being written into the DB, where the encryption library will be in your application. But it's not fool proof, and it'll mightily slow down all data access.

SG
Aham Brahmasmi!

Time zone in SQL Server

Goutam Patra30-Aug-10 23:57

30-Aug-10 23:57

I am onto a project of backoffice management of International stock exchanges. I need to manage trades of different stock exchanges there. The date and time I am getting from exchange is according to their time zone. Further I need to calculate some thing using their time. Some of reports I need to generate after converting the time to my time zone that is IST (I am from India).

Now what I have in my mind is to store the time provided by the exchange with the time zone (of the exchange) and also the converted (to IST) time.

I am looking for some idea how to store the time zone and the converted time into database.

Is there any facility in SQL server to time between time zones or I have to keep the time gap between zones?

I have found
SQL 2005 Time Zone Conversion Functions[^]
and
http://msdn.microsoft.com/en-us/library/ms145276%28SQL.90%29.aspx[^]

But, what would be the best practice to do such thing?

Richard MacCutchan31-Aug-10 1:05

Richard MacCutchan

31-Aug-10 1:05

The best method for dealing with data from different time zones is to store all time values as UTC times (i.e. zone 0). Where necessary keep also a note of the time zone offset for the record, or the particular account customer. You can then calculate time differences in absolute terms when trying to sort transactions into time order etc. When producing reports for consumers you should add their personal time zone offset to the time values, so the consumer sees report data in their own time zone.

It's time for a new signature.

Goutam Patra31-Aug-10 2:51

31-Aug-10 2:51

Yes I agree. Actually I was in a bit dilemma because I will get the data from exchange side (they are providing flat files) will be in their time zone. So I need to convert it into UTC first. But in some day end calculations I need to use their time also, so in that time I need to convert it again into their time zone.
However perhaps I will store it in UTC format ultimately.

Thank you Richard

Richard MacCutchan31-Aug-10 6:44

Richard MacCutchan

31-Aug-10 6:44

As a general rule you should never store times in a localtime format, they should always be stored as UTC values. This allows you to manipulate them in any way necessary, time difference, sorting etc. It is only necessary to convert to localtime when you wish to display it for the end user irrespective of what time zone that user is in.

It's time for a new signature.

Goutam Patra31-Aug-10 19:27

31-Aug-10 19:27

OK. thank you.

dan!sh 31-Aug-10 1:06

dan!sh

31-Aug-10 1:06

While saving the time from another time zone, just save value returned by GetDate function. It gives current time in the current timezone. In case you are looking for GMT times, use GetUtcDate function.

Goutam Patra31-Aug-10 2:53