Newbie question about creating a run-time only database

[Guest]

Hi all

I have started writing a database using Access. Is it at all possible
to create a run-time version of the final database/code. A friend of
mine wants to have the final product but doesn't have Access on his
computer. What do I need to do? (I want to keep legal with all the
licensing conditions)

I know with Visual Basic it is possible to convert a VB programme to a
..exe file and then give that file to another person (along with a few
freely available .dlls etc) How can I do a similar thing with Access?

Thanks

 

[Rick Brandt]

Hi all

I have started writing a database using Access. Is it at all possible
to create a run-time version of the final database/code. A friend of
mine wants to have the final product but doesn't have Access on his
computer. What do I need to do? (I want to keep legal with all the
licensing conditions)

I know with Visual Basic it is possible to convert a VB programme to a
.exe file and then give that file to another person (along with a few
freely available .dlls etc) How can I do a similar thing with Access?

The Developer's Version of Office allows you to create and distribute an
Access Runtime, but it would be cost prohibitive to do unless you are
distributing "at least several" copies. Any less than that and it would be
cheaper to just buy licensed copies of Office. Especially if you consider
the extra time and trouble into the equation.

 

[Guest]

Oh dear! I was hoping that there might be a cheaper solution, even
buying an add-on, or something like that to achieve the result I
wanted. Perhaps the answer might be to develop a cruder solution in
Visual Basic and distribute the resultant database/code that way.

Many thanks for the reply.

 

[M.L. Sco Scofield]

That would be your other option.

Sorry about that.

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #15 of 19: 5 dialogues = 1 decalogue
Miscellaneous Access and VB "stuff" at www.ScoBiz.com

 

[bOOyah]

Oh dear! I was hoping that there might be a cheaper solution, even
buying an add-on, or something like that to achieve the result I
wanted. Perhaps the answer might be to develop a cruder solution in
Visual Basic and distribute the resultant database/code that way.

Many thanks for the reply.

That's similar to the position in which I find myself: because my target
audience doesn't have Access licenses I'm opting to create an MDB file
containing only the database tables, but code all the application
"smarts" in a .NET Windows application. Then I'll ship the .NET app +
MDB file. Can anyone tell me if that's also legal? Probably not,
knowing my luck.

I'm starting to understand the popularity of FoxPro... ;-)

 

[Douglas J. Steele]

That's similar to the position in which I find myself: because my target
audience doesn't have Access licenses I'm opting to create an MDB file
containing only the database tables, but code all the application
"smarts" in a .NET Windows application. Then I'll ship the .NET app +
MDB file. Can anyone tell me if that's also legal? Probably not,
knowing my luck.

AFAIK, there are absolutely no restrictions around using a Jet database
(i.e.: .MDB file) strictly to store data, and getting at that data from some
other application.

I'm starting to understand the popularity of FoxPro... ;-)

I'll pretend I didn't hear that. <g>