[AccessD] Amortization

Mike and Doris Manning mikedorism at ntelos.net
Fri Aug 15 12:25:41 CDT 2003


As Emeril Legasse says "Now you are cooking with gas!"  This is the level of
information that Paula needed from the beginning.  

I knew you had it in you Charles!  Just had to drag it out of you before she
wasted time traveling down the wrong path...

Doris Manning
Database Administrator
Hargrove Inc.
www.hargroveinc.com


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Wortz, Charles
Sent: Friday, August 15, 2003 12:46 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Amortization


Doris,

Maybe I didn't make myself clear.  The conversion process is not part of the
deployment package, it is a one-time only step in the development process.
This is only done on Paula's computer that has ODE, Access, and Excel.

Presumably Paula has an Excel spreadsheet that does amortization.  She needs
to import and convert the Excel macros in that spreadsheet into Access and
make them an Access VBA module.  All references to Excel objects will need
to be converted to equivalent Access objects.  When she has done all that,
instead of an Excel spreadsheet where the user enters the data to use in the
calculation, she will have an Access form where the user enters the data to
be used.  Some of the functions used in the Excel amortization spreadsheet
may have exact equivalents in the Access financial functions.  Some she may
have to write code to perform the same function since there is not
equivalent in the Access financial functions library.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us



-----Original Message-----
From: Mike and Doris Manning [mailto:mikedorism at ntelos.net] 
Sent: Friday 2003 Aug 15 11:24
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Amortization

How will that help her Charles?

She can't use CreateObject or GetObject as part of her automation code
because it won't work on a computer that doesn't have Excel installed.

Short of creating an Access report that does what the Excel spreadsheet
does, what she is trying to do cannot be legally done if the user doesn't
have Excel installed.

Doris Manning
Database Administrator
Hargrove Inc.
www.hargroveinc.com


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Wortz, Charles
Sent: Friday, August 15, 2003 12:05 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Amortization


Paula,

This is the reason I suggested converting the Excel macros to Access VBA
modules so you do not need the Excel object library.  You will be using the
Access object libraries which you do have the right to distribute if you
have ODE.

Charles Wortz

-----Original Message-----
From: Mike and Doris Manning [mailto:mikedorism at ntelos.net] 
Sent: Friday 2003 Aug 15 10:43
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Amortization

Office Developer only gives you the right to distribute the Access run-time
engine which is necessary for a user to run your Access program if they
don't have Access on their system.  This was done because users had a choice
to buy just Office or Office Pro (which included Access).

It does not give you the right to redistribute an Access database that uses
the Word or Excel object models to a user who does not have Word or Excel
installed on their system.  You do not have a legal right to install or
distribute the object libraries involved to a user who doesn't have them.

Doris Manning
Database Administrator
Hargrove Inc.
www.hargroveinc.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paula Wright
Sent: Friday, August 15, 2003 11:04 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Amortization


Even if you have Office Developer - which of course you would if you were
going to create a run-time?

-----Original Message-----
From: Mike and Doris Manning [mailto:mikedorism at ntelos.net] 
Sent: Friday, August 15, 2003 11:03 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Amortization


Please note that this WILL NOT work if the end-user doesn't have Excel. You
CANNOT LEGALLY DISTRIBUTE the Excel Object Model even if you include it in
your Access run-time.

Doris Manning
Database Administrator
Hargrove Inc.
www.hargroveinc.com


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paula Wright
Sent: Friday, August 15, 2003 10:51 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Amortization


I will try this.  You don't happen to know of any examples anywhere, do you?

Thanks,
Paula

-----Original Message-----
From: Wortz, Charles [mailto:CWortz at tea.state.tx.us] 
Sent: Friday, August 15, 2003 10:43 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Amortization


Paula,

If they don't have Excel installed, then you can copy the Excel macros into
Access and convert them to a module that you will run instead.

Charles Wortz
-----Original Message-----
From: Paula Wright [mailto:paulawright at boddienoell.com] 
Sent: Friday 2003 Aug 15 09:30
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Amortization

You can do this without Excel being installed on the PC?

Paula
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list