Access and InfoPath

[Jonjon]

I was wondering if the 2 are compatable. Or if there are advantages to using
them together, or if InfoPath is a separate solution. Do I need a separate
server for either of them?

I work for a mortgage brokerage (in Canada), and I just started creating a
database in Access to track lenders products, mortgage insurance products,
applicants information, marketing campaigns, etc.

I was trying to figure out if InfoPath would be useful for creating and
using a mortgage application form to use via e-mail, or a webpage, or even on
my laptop.

Thanks in Advance

Paul

 

[Arvin Meyer [MVP]]

I was wondering if the 2 are compatable. Or if there are advantages to
using
them together, or if InfoPath is a separate solution. Do I need a
separate
server for either of them?

I work for a mortgage brokerage (in Canada), and I just started creating a
database in Access to track lenders products, mortgage insurance products,
applicants information, marketing campaigns, etc.

I was trying to figure out if InfoPath would be useful for creating and
using a mortgage application form to use via e-mail, or a webpage, or even
on
my laptop.

The 2 can be used together. You may want to ask this in an InfoPath
newsgroup, since they should have a better idea of how to connect them.

 

[Jonjon]

Thanks I took your advice and posted on InfoPth forum.

I was also wondering, I noticed here on the forums alot of people using
Access as a front end and SQL as a back end. Is this necessary, or can
Access be used as a stand alone database program?

 

[Arvin Meyer [MVP]]

JET is the standard database engine that comes with Access. Actually, the
overwhelming majority of databases in the world are Access/JET. They
outnumber all other database combined. So the answer is yes, of course.

Keep in mind that a SQL-Server back-end is preferable if there is a need to
for:

1. High level security.
2. 24/7 operation with little maintenance time.
3. A large (more than 20 to 50) number of users.
4. A large sized database with millions of records.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[David W. Fenton]

Keep in mind that a SQL-Server back-end is preferable if there is
a need to for:

1. High level security.
2. 24/7 operation with little maintenance time.
3. A large (more than 20 to 50) number of users.
4. A large sized database with millions of records.

Or a smaller number of records with BLOBs in them -- the key point
is that a Jet MDB cannot exceed 2GBs in size (and if it gets
anywhere close, you better watch out; anything over 1GB looks like a
candidate for upsizing to me).

 

[Jonjon]

Very good information guys.

Thanks a lot.

Paul

Or a smaller number of records with BLOBs in them -- the key point
is that a Jet MDB cannot exceed 2GBs in size (and if it gets
anywhere close, you better watch out; anything over 1GB looks like a
candidate for upsizing to me).