I have two small databases that I have been doing all development in Access

2000.  I'm looking at the option of turning them into VB Applications using

Access as the database. I think this will give me more protection of the

source code.



I would like thoughts from others about this.



Cheryl Owens

COLSA Corporation

cheryl.owens@l...

cowens@c...

xxx-xxx-xxxx

Cheryl,



I should preface my comments by saying I am a VB programmer hence

somewhat biased.  That done with, my opinion is I agree

%100.  VB application are faster than Access applications (they only

call the database as necessary as opposed to living in the database.  It

is also very easy to control sourcecode from VB.  I also find VB easier

to use.  Lastly, if you build your VB app properly (multi-tier

solution), reusing components is a snap thereby shortening development

time of similar Applications. 



The only drawback is VB is a more expensive solution (though

distributing is cheaper as the client does not need Access; they should

only read the database through your app).  You have to have both Access

and VB as opposed to just Access.  If the money issue does not bother

you I recommend it strongly.



Yehuda



-----Original Message-----

From: Owens Cheryl A (Contractor) [mailto:cheryl.owens@l...]

Sent: Wednesday, September 12, 2001 3:10 PM

To: Access

Subject: [access] VB Application





I have two small databases that I have been doing all development in

Access 2000.  I'm looking at the option of turning them into VB

Applications using Access as the database. I think this will give me

more protection of the source code.



I would like thoughts from others about this.



Cheryl Owens

COLSA Corporation

cheryl.owens@l...

cowens@c...

xxx-xxx-xxxx







---

You are currently subscribed to access as: yehuda@i... To

unsubscribe send a blank email to $subst('Email.Unsub')

Cheryl



If source code security is your only concern, why not 'compile' your 

database into an mde file? It won't prevent the users from looking at 

your queries and tables, but will protect forms, reports and modules.



-BDS



-----Original Message-----

From:	Owens Cheryl A (Contractor) [SMTP:cheryl.owens@l...]

Sent:	12 September 2001 20:10

To:	Access

Subject:	[access] VB Application



I have two small databases that I have been doing all development in 

Access

2000.  I'm looking at the option of turning them into VB Applications 

using

Access as the database. I think this will give me more protection of the

source code.

I'd go for it, although I dislike VB as compared to Access, and find it much

tougher to work in. However, you've seen exactly the opposite opinion in

another response to your question. That's why you should give it a try -

find out how you like working in VB.



For sure it'll be faster an more secure than Access. Even an Access mde

exposes queries.



Peter



> -----Original Message-----

> From: Owens Cheryl A (Contractor) [mailto:cheryl.owens@l...]

> Sent: September 13, 2001 2:10 AM

> To: Access

> Subject: [access] VB Application

>

>

> I have two small databases that I have been doing all development

> in Access

> 2000.  I'm looking at the option of turning them into VB

> Applications using

> Access as the database. I think this will give me more protection of the

> source code.

>

> I would like thoughts from others about this.

>

> Cheryl Owens



>