Greetings. I have many accounting systems developed in Access. I want to
go
to a web based system.
Ms-access is part of the office suite. Word, Excel, or ms-access for that
matter has little to do with web based systems.
I understand about creating Active Server Pages, using
SQL, FrontPage, or PHP, apache and mySQL.
If you understand the above, then how can you be confused about sql?
Ms-access uses sql for reports, for forms, for combo boxes, for listbox...in
virtually just about everything you do in ms-access involves using sql. And,
for web sites that use a lot of data, then they also use sql for just about
everything also. (you seem to be hinting that sql is some magical thing out
there that you don't know about?).
But I am confused about one thing. I created many one-to-many
relationships,
which have forms and subforms. Now I read that to do this, you need to use
something like Oracle or PostgresSQL, because of transactions.
Why do you need oracle? Any good developer will often use transactions (you
can use them in ms-access if you want. Check out BeginTrans, CommitTrans,
Rollback Methods in the ms-acess help). The fact that you been using and
working with relatonships and sql in ms-access all along means you don't
need Oracle to have a one to many relatonship. The above question seems very
confusing?
I am brand new to this conversion, but is this wrong? I have to do the
form/subform to make my things work right.
ms-access is about the only product in the marketplace that supports sub
forms (I don't know of any other product that has this feature). So,
clearly, all of the accounting and other systems out there work just fine
without sub forms. So, I see no reason why you "have to do this frm/subfrom"
thing. What you have to do is use a different development approach. In fact,
you have to use whatever the tools at your disposal give you. There is a ton
of applications written in Visual Basic..but Visual basic does not have
sub-forms. In fact, did you know that Simply Accounting uses a ms-access
database..but was written in Visual Basic? (you can actually open Simply
Accounting files with ms-access!!). The fact that Visual Basic does not have
sub-forms never hurt the VB dev eloeprs.
Could someone help me, and point
me in the direction of some sample web databases to try?
web databases? That is a strange term. You mean you want to try an
application that runs on the web, and it is connected to a database? (that
seems like a more reasonable request here). Heck, just go to
www.amazon.com
and order a book...
Heck...go to any site on line that allows you to shop and purchase things.
Any one of those sites that allows you fill up a shopping cart with many
items for you ONE order is thus a classic one to many relationship that is
driven by a database. While
www.amazon.com, or most of these systems don't
use a form with a sub-form, they work fine (and, as mentioned, VB developers
also never had sub-forms).
There is no question if I was making a book ordering system in ms-access
then I likely would use a form and sub-form. I would do this because I have
that kind of nice feature. However, on a web based system, you don't really
have the ability to make such nice forms. However, this does not means that
you can't have ONE order on amazon.com and place "many" books into that
single order.
Since the developers and designs of the amazon.com site did not have a form
+ sub-form..then they took a different approach.
So, if you are looking for some ideas of web sites that have one thing, and
then have "many" things (like a form + sub form), then just go to virtually
any web site that allows you to shop.....
Web based applications don't have such an ability to produce nice interfaces
like a rich windows product like ms-access, so, you as a developer have to
change how you design the interface. As mentioned, just go to any shopping
site on the web to get ideas.
However, developing, and building and writing web based systems has little
to do with ms-access and this newgroup.
