A
Armstrong Wong
1. What's the difference between Access 2002 and Visual FoxPro 7/8?
2. Is Access programmable like VFP?
Armstrong
2. Is Access programmable like VFP?
Armstrong
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
L
Larry Linson
"Armstrong Wong" wrote
They are separate, different database management software products, both
produced by Microsoft. VFP is descended from the "xBase" database world, but
now looks very little like the old DOS dBase and clones you may remember.
VFP has a dedicated following of developers and, perhaps, "power users" --
it isn't for the novice or casual database user. Access is database
management software that has a very "visual" user interface, is unarguably
the most widely-distributed database of all time, can be effectively used by
everyone from the novice/casual user to the developer.
Both VFP and Access can be used alone or as clients to server databases.
Access, without a server database, can be used by multiple users (I don't
know if VFP has a multiuser capability, but suspect it does.)
Yes, and it shares the Visual Basic for Applications (VBA) language with
other Office software, other software from Microsoft, and other software
from third parties. VFP's programming language, as far as I know, is unique
to VFP. I'm not sure how successfully you can use VFP _without_ programming,
but one of my Access colleagues created a database for ordering food, and
tracking the orders, for the food service of a large metropolitan school
district. It has been successfully used for over 10 years, now, and he says
the only VBA code in it was that automatically generated by the control
wizards. So you can easily point-and-click your way to a relatively complex
application without using the programming capability. Many of us, however,
use VBA because we want the ability to field and handle errors that may
occur and VBA code allows that.
For a link to a whitepaper on "choosing the appropriate database", a few
years out of date, but whose major points are still valid, see the Knowledge
Base article at
http://support.microsoft.com/default.aspx?scid=kb;[LN];168549.
Larry Linson
Microsoft Access MVP
1. What's the difference between
Access 2002 and Visual FoxPro 7/8?
They are separate, different database management software products, both
produced by Microsoft. VFP is descended from the "xBase" database world, but
now looks very little like the old DOS dBase and clones you may remember.
VFP has a dedicated following of developers and, perhaps, "power users" --
it isn't for the novice or casual database user. Access is database
management software that has a very "visual" user interface, is unarguably
the most widely-distributed database of all time, can be effectively used by
everyone from the novice/casual user to the developer.
Both VFP and Access can be used alone or as clients to server databases.
Access, without a server database, can be used by multiple users (I don't
know if VFP has a multiuser capability, but suspect it does.)
2. Is Access programmable like VFP?
Yes, and it shares the Visual Basic for Applications (VBA) language with
other Office software, other software from Microsoft, and other software
from third parties. VFP's programming language, as far as I know, is unique
to VFP. I'm not sure how successfully you can use VFP _without_ programming,
but one of my Access colleagues created a database for ordering food, and
tracking the orders, for the food service of a large metropolitan school
district. It has been successfully used for over 10 years, now, and he says
the only VBA code in it was that automatically generated by the control
wizards. So you can easily point-and-click your way to a relatively complex
application without using the programming capability. Many of us, however,
use VBA because we want the ability to field and handle errors that may
occur and VBA code allows that.
For a link to a whitepaper on "choosing the appropriate database", a few
years out of date, but whose major points are still valid, see the Knowledge
Base article at
http://support.microsoft.com/default.aspx?scid=kb;[LN];168549.
Larry Linson
Microsoft Access MVP
V
Van T. Dinh
See comments in-line.
HTH
Van T. Dinh
MVP (Access)
applications and therefore the materials covered is
basically the introduction to each sofware application.
Remember, Microsoft Press also published Microsoft Access
XP Inside Out which covers only Access XP and it is about
3/4 as thick as the Office XP Inside Out. On top of that,
Microsoft Press also published other books on Access,
Access & SQL Server, ADO, etc ...
In fact, I haven't found any book that covers *everything*
in Access. There are so much you can discover by
yourself...
Access. Access uses the JET database engine but Access is
a separate entity from JET. AFAIK, there is no Access
version for Windows CE AFAIK.
prgramming which present logical, structured information
on Access programming basics rather than runnig around
with URL and no URLs will be as comprehensive. URLs tend
to focus on very specific topics which is useful when you
want to focus on a particular topic.
FollowHyperlink Method.
HTH
Van T. Dinh
MVP (Access)
This book tries to cover 7-8 different sofware-----Original Message-----
Larry,
Thanks for your quick reply. I was a Clipper developer. I didn't know Access
is programmable. I thought Access is just a simple drag- and-drop form
generator. I'm amazed that Access can be used in food service application.
When I read Microsoft Office XP Inside Out by Michael Halvorson and Michael
Young, the book didn't hint the awesome capability such as VBA you highlight.
It just covers the usual boring topics such as creating databases and reports.
It's hardly "inside out" per se.
applications and therefore the materials covered is
basically the introduction to each sofware application.
Remember, Microsoft Press also published Microsoft Access
XP Inside Out which covers only Access XP and it is about
3/4 as thick as the Office XP Inside Out. On top of that,
Microsoft Press also published other books on Access,
Access & SQL Server, ADO, etc ...
In fact, I haven't found any book that covers *everything*
in Access. There are so much you can discover by
yourself...
Be careful here. Most of these are JET databases and notMy interest in Access is heightened by the discovery that most Windows CE
database application (for pocket PC and handheld PC) tends to rely on Access.
Access. Access uses the JET database engine but Access is
a separate entity from JET. AFAIK, there is no Access
version for Windows CE AFAIK.
You are probably better of with a book or 2 on Access1. Would you be very kind enough to suggest some useful URLs (other than
newsgroups) on the internet so that I can learn more about Access programming?
prgramming which present logical, structured information
on Access programming basics rather than runnig around
with URL and no URLs will be as comprehensive. URLs tend
to focus on very specific topics which is useful when you
want to focus on a particular topic.
Yes, you can use hyperlink fields or you can use2. Can Access database field support URL such that a user just double-click
the field to activate the corresponding webpage, say www.microsoft.com?
FollowHyperlink Method.
A
Armstrong Wong
Van,
Many thanks for your big help.
for sychronization (with desktop) and ODBC connection.
2. Access is widely used for retrieving data stored in Database Object Store
in WinCE device (main memory), AFAIK. Please correct me if I'm wrong.
Yes, I'll rush to Amazon.com to buy some ebooks on Access.
Thanks again.
Armstrong Wong
Hong Kong
Many thanks for your big help.
I didn't know Access is based on JET database.Be careful here. Most of these are JET databases and not
Access. Access uses the JET database engine but Access is
a separate entity from JET.No,
1. To be precise, it's a combination of Access + Pocket Access, which are usedAFAIK, there is no Access version for Windows CE AFAIK.
for sychronization (with desktop) and ODBC connection.
2. Access is widely used for retrieving data stored in Database Object Store
in WinCE device (main memory), AFAIK. Please correct me if I'm wrong.
Yes, I'll rush to Amazon.com to buy some ebooks on Access.
Thanks again.
Armstrong Wong
Hong Kong
V
Van T. Dinh
See comments in-line.
HTH
Van T. Dinh
MVP (Access)
files is the JET engine but you can use other database
engines with Access instead of JET. In the second case,
Access acts more like the Front-End development software.
actually with Palm OS and Pendragon rather than Windows CE
and Pocket Access.
For Palm OS + Pendragon, my understanding is that the JET
mdb file resides on both the host PC and the Palm
handheld. When you "hot-synch" the Palm handheld, the 2
copies of the mdb will be synchronised. You can, of
course, use Access to retrieve the data in the mdb file
which resideson the host PC.
HTH
Van T. Dinh
MVP (Access)
The default database engine for Access database (mdb)-----Original Message-----
I didn't know Access is based on JET database.
files is the JET engine but you can use other database
engines with Access instead of JET. In the second case,
Access acts more like the Front-End development software.
Yes, I think this is more accurate.1. To be precise, it's a combination of Access + Pocket Access, which are used
for sychronization (with desktop) and ODBC connection.
My limited (very beginning of the project) experience is2. Access is widely used for retrieving data stored in Database Object Store
in WinCE device (main memory), AFAIK. Please correct me if I'm wrong.
actually with Palm OS and Pendragon rather than Windows CE
and Pocket Access.
For Palm OS + Pendragon, my understanding is that the JET
mdb file resides on both the host PC and the Palm
handheld. When you "hot-synch" the Palm handheld, the 2
copies of the mdb will be synchronised. You can, of
course, use Access to retrieve the data in the mdb file
which resideson the host PC.
A
Albert D. Kallal
You can get a run down of some of the features of the office developer
edition at:
http://www.microsoft.com/office/developer/suite/fastfacts.asp
You want to note that the programming language you use in ms-access is VB.
It is actually called VBA (Visual Basic for Applications).
However, the syntax, and the development environment of access is really the
same as VB. The major difference is that access has a different forms model,
and ms-access can't be used to write com objects. Since both VB and
ms-access completely function around the "forms" that you make, then while
the language syntax between VB and VBA is the same, there is a big
difference DUE TO the forms being different in VB and ms-access.
Thus, you have a full VB development system available in ms-access. The real
advantage of VBA in ms-access is that you are actually learning VB. When you
learn ms-access, then you are one leg up on knowing VB. Further, Word, Excel
etc also use VBA for their programming language. So, your skills that you
learn in ms-access are transferable to VB programming language, and the rest
of the office suite.
The major programming difference between access and VFP is that VFP is a
full Object Orientated development platform.
ms-access is just like VB, and VB supports the creating of Class objects.
Thus you can crate class objects in ms-access, but like VB, it is not a true
OO language. I certainly do create class objects a lot in ms-access, and
thus is does give you a the first steps towards making the OO jump.
As for the comments about pocket access? No, the use of the term "pocket
access" has always been a real confusing point. There is a an ability to
transfer data from access file to the pocket pc, but this really has zero
relation to ms-access as a development tool. You can only transfer data, but
any thing like forms and the user interface on the pocket pc must be
programmed in a language (such as embedded VB, or embedded c). There are
also a number of database development systems that you can purchase for the
pocket pc, but ms-access is not one of them.
edition at:
http://www.microsoft.com/office/developer/suite/fastfacts.asp
You want to note that the programming language you use in ms-access is VB.
It is actually called VBA (Visual Basic for Applications).
However, the syntax, and the development environment of access is really the
same as VB. The major difference is that access has a different forms model,
and ms-access can't be used to write com objects. Since both VB and
ms-access completely function around the "forms" that you make, then while
the language syntax between VB and VBA is the same, there is a big
difference DUE TO the forms being different in VB and ms-access.
Thus, you have a full VB development system available in ms-access. The real
advantage of VBA in ms-access is that you are actually learning VB. When you
learn ms-access, then you are one leg up on knowing VB. Further, Word, Excel
etc also use VBA for their programming language. So, your skills that you
learn in ms-access are transferable to VB programming language, and the rest
of the office suite.
The major programming difference between access and VFP is that VFP is a
full Object Orientated development platform.
ms-access is just like VB, and VB supports the creating of Class objects.
Thus you can crate class objects in ms-access, but like VB, it is not a true
OO language. I certainly do create class objects a lot in ms-access, and
thus is does give you a the first steps towards making the OO jump.
As for the comments about pocket access? No, the use of the term "pocket
access" has always been a real confusing point. There is a an ability to
transfer data from access file to the pocket pc, but this really has zero
relation to ms-access as a development tool. You can only transfer data, but
any thing like forms and the user interface on the pocket pc must be
programmed in a language (such as embedded VB, or embedded c). There are
also a number of database development systems that you can purchase for the
pocket pc, but ms-access is not one of them.
J
Joan Wild
Albert D. Kallal said:As for the comments about pocket access? No, the use of the term "pocket
access" has always been a real confusing point. There is a an ability to
transfer data from access file to the pocket pc, but this really has zero
relation to ms-access as a development tool. You can only transfer data, but
any thing like forms and the user interface on the pocket pc must be
programmed in a language (such as embedded VB, or embedded c). There are
also a number of database development systems that you can purchase for the
pocket pc, but ms-access is not one of them.
Not to muddy the waters, but I thought Pocket Access was a cut-down version
of Access that runs on a handheld PC (as opposed to a palm-sized PC).
T
Tony Toews
Joan Wild said:Not to muddy the waters, but I thought Pocket Access was a cut-down version
of Access that runs on a handheld PC (as opposed to a palm-sized PC).
It's my understanding that Pocket Access is incredibly simple, lame
and no longer available.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
A
Albert D. Kallal
"Tony Toews" <[email protected]
Correct, in fact, Pocket access was only the conduit..there was NO UI
part...
It's my understanding that Pocket Access is incredibly simple, lame
and no longer available.
Correct, in fact, Pocket access was only the conduit..there was NO UI
part...
T
Tony Toews
Albert D. Kallal said:Correct, in fact, Pocket access was only the conduit..there was NO UI
part...
I didn't even know that much.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.