Please ANSWER ASAP--need to know today.

  • Thread starter Thread starter SStory
  • Start date Start date
S

SStory

I am a Visual Basic programmer. I am used to programming with SQL Server or
Access with a Visual Basic Front end.

I have the opportunity to take on a project in Access. I am not sure the
size of the project but it is for a maintenance department in a
manufacturing plant.

I have used Access for very simple projects. I have used MDB files as the
database with a VB front end.

My questions are:

1.) Would it be very difficult for a VB Programmer with limited Access
experience to pick this up quickly? And what books would be recommended for
learning about the various issues, including good form design?

I know how to design the database, make queries and simple forms, just
sometimes complex forms take me a while to figure out. I thought there
might be a good resource on it.

2.) How does access handle more than one user? I am not sure if this
database will be single or multiuser but wanted to know if I would have to
do some special things for multiple users on a network?

3.) I know nothing about Access database security other than setting a
password for the entire database. Any recommendations on that?

4.) When people speak of splitting front end and back end, is that possible
with the normal version of access or is that only with the developer
version?

Again, I have used VB for since version 4.0... and written a few simple
Access apps...just seems maybe there are some areas I know nothing about and
wondering if I should attempt this.

I really need an answer today as I have to accept the contract tomorrow if I
want it.

Thanks kindly,

Shane
 
Please see in-line comments:

SStory said:
I am a Visual Basic programmer. I am used to programming with SQL Server or
Access with a Visual Basic Front end.

I have the opportunity to take on a project in Access. I am not sure the
size of the project but it is for a maintenance department in a
manufacturing plant.

I have used Access for very simple projects. I have used MDB files as the
database with a VB front end.

My questions are:

1.) Would it be very difficult for a VB Programmer with limited Access
experience to pick this up quickly? And what books would be recommended for
learning about the various issues, including good form design?

I know how to design the database, make queries and simple forms, just
sometimes complex forms take me a while to figure out. I thought there
might be a good resource on it.
Click to expand...
If you are experienced in VB, I can't see you having too many problems in
Access, it is very similar to VB, There are a few gotcha's, but nothing a
good VB programmer shouldn't be able to handle. There are lots of resouces
on Access programming
http://msdn.microsoft.com/library/d.../en-us/bapp2000/html/acbatitle.asp?frame=true

have a quick trawl through Google.
2.) How does access handle more than one user? I am not sure if this
database will be single or multiuser but wanted to know if I would have to
do some special things for multiple users on a network?
Click to expand...

Multiple users are no problem in my experience.
3.) I know nothing about Access database security other than setting a
password for the entire database. Any recommendations on that?
Click to expand...

Look into .MDW files, they cover user/group security.
4.) When people speak of splitting front end and back end, is that possible
with the normal version of access or is that only with the developer
version?
Click to expand...

Any version.
You just have one Database with all the tables, and a second with LINKS to
the tables, and containing all the queries, forms etc.
Again, I have used VB for since version 4.0... and written a few simple
Access apps...just seems maybe there are some areas I know nothing about and
wondering if I should attempt this.
Click to expand...

Don't really know what to suggest. If you are experienced in VB, and know
your way around Access, (creating forms, grids etc.) then you should be OK.
Then again, it depends on the complexity of the project you're considering
taking on, and if your deadline will give you enough time to work through
any difficulties you come across...
 
Having done both, VB programming and Access, I find the two very similar.
When you build forms and reports in access its very similar to building a
form in VB. Same sorta drag drop the textbox, label, etc.. Then assign
code, but in Access its assign it to a field in a query or table, or even VB
code. I don't think you should have any problem picking up Access. As far
as multi users that is really easy, and many good examples of multi user
examples with passwords out there. As was already answered splitting can be
done with any version. Also the database design takes some practice to have
a efficient multi table database. Newbies tend to put everything in one
table and it grows fast and slow. Again many good access books from barnes
and noble or amazon, many for newbies. My current favorite is Microsoft
Access 2003 inside/out by John L. Viescas. Your biggest challenge is if you
are going to write a VB front end for a very complex access database. The
developer version of access however would allow you to compile the database
to a format where people do not need to have access installed on there
machines.
 
Access is great database for a multi-user enviroment.
Simple to set up and use. To set up security first split
the database into a front-end/back-end (use this by using
the database splitter (tools/database utilities/database
splitter)) You can use a wizard for everything that you
want to do. I would suggest not using an overall database
password since it is so easy to lose/forget one password.
You can split the database with the normal version of
access. When you use it in a multiuser enviroment make
sure that the back-end resides on the network (shared full
access to all users) and the front end will reside on the
individuals desktop as a short cut.
My suggestion is read through the access security
newsgroup and it will give you a good idea at what other
peoples problems are and what you can do to prevent them
from happening. As for the books, there are so many out
there that contain the same info, plan on spending at
least $40 on one. Good to have and reference though. If
you can't find it in there, post the question here and
someone will answer. Good luck!

Mike
 
Thanks,

And since I haven't been given any details. I don't know either. They just
looked at my resume and said I should be able to.

I am very experienced at VB. I have done a few forms in Access.
I have trouble sometimes with forms that have subforms, linking them
correctly, etc.
I think I am missing something there in making the connection.

I have no trouble reporting or with queries.

Thanks,

Shane
 
The
developer version of access however would allow you to compile the database
to a format where people do not need to have access installed on there
machines.
Click to expand...

For clarification with respect to end-users not having Access on their
machines - the developer edition (now the "Microsoft Office Access 2003
Developer Extensions" included with the "Microsoft Visual Studio Tools for the
Microsoft Office System" that is available separate from MS Office) provides the
Access RunTime files (with a license to distribute) and a way to install it
along with your application. There is no "format" in compiling an Access
application for those who don't have Access. The RunTime files *are* Access and
are the minimum requirement to run an Access application.
 
Thanks for you answer. I have db design experience in SQL Server and Access.
Just the UI/and multiuser issues and MDE if these people decide they want
that, that concern me.

I haven't been told the specs, just offered the job if I want to give it a
whirl. So I just wanted to make sure I would be able to.

Again I have made access databases, queries, reports and simple forms. When
they get into subforms and the like in Access I could use a little help
knowing how to get them to refresh and all at times--at least had that
problem on one that I created.

If this is a simple one or two user db then all my concerns are probably for
naught... Since I don't yet have that info... I wanted to check with you
guys.

Thanks for all the responses.

Shane
 
Thanks Mike.


Mike said:
Access is great database for a multi-user enviroment.
Simple to set up and use. To set up security first split
the database into a front-end/back-end (use this by using
the database splitter (tools/database utilities/database
splitter)) You can use a wizard for everything that you
want to do. I would suggest not using an overall database
password since it is so easy to lose/forget one password.
You can split the database with the normal version of
access. When you use it in a multiuser enviroment make
sure that the back-end resides on the network (shared full
access to all users) and the front end will reside on the
individuals desktop as a short cut.
My suggestion is read through the access security
newsgroup and it will give you a good idea at what other
peoples problems are and what you can do to prevent them
from happening. As for the books, there are so many out
there that contain the same info, plan on spending at
least $40 on one. Good to have and reference though. If
you can't find it in there, post the question here and
someone will answer. Good luck!

Mike
Click to expand...
 
Well,

I don't know the specs for the project, unfortunately.. They just looked at
my resume and spoke to IT and said job's yours if you want it. It is
contract and they don't know how long it will take so....seems not a major
deadline.

Guess if I take it, I can ask you guys a lot of dumb questions and figure it
out if I have problems.

Thanks,

Shane
 
SStory said:
I am very experienced at VB. I have done a few forms in Access.
I have trouble sometimes with forms that have subforms, linking them
correctly, etc.
I think I am missing something there in making the connection.
Click to expand...

I suspect you are missing something. <smile>

Until I understood exactly what was happening with the foreign keys
and primary keys on the table subforms were causing me troubles.
Fortunately relational integrity messages ensured I finally got it
correct.

Tony
 
Thanks to the group for all the comments.

I bought a 1,500 page book on it by Roger Jennings.

It seems to be very good and is explaining a lot to me.

I will try to read it all and come back with questions if I have other
needs.

Thanks again,

Shane
 
Back
Top