Re: Recomended front ends?

All,

No Web driven, but . . . . we’ve had some success with using LibreOffice(calc) as a frontend. Fairly easy to build forms, etc. Only limited experience so far, but was able to build domain lists from SQL calls, for form pulldown lists, etc.

bobb

> On Aug 8, 2019, at 2:10 PM, Rich Shepard <rshepard(at)appl-ecosys(dot)com> wrote:
>
> Think Before You Click: This email originated outside our organization.
>
>
> On Thu, 8 Aug 2019, Tim Clarke wrote:
>
>> We tried Django without any pleasant results.
>
> Tim,
>
> That's unexpected and too bad.
>
>> I'd also caution using MS Access, we're desperate to get away from it.
>> Sharing code has challenges and it is horribly aggressive with caching
>> unless you use un-bound forms and write all the CRUD interface code
>> yourself.
>
> Slightly off-topic, but I've not seen anything good about Access. My
> understanding is it's a flat-file database intended as a user front end to
> Microsoft's relational database product. My experiences with those who use
> it have been painful.
>
> Just yesterday I downloaded a very large database of fisheries data from a
> federal agency and have started translating it to postgres using the
> mdbtools. There's no schema provided, only 32 pages of table columns and
> types without descriptions of the column names. No primary keys, no foreign
> keys, and only 66 tables were found in the .mdb file while all table names
> starting with s through z were not available. There are also many tables
> that hold redundant data which should not exist as the contents are easily
> generated by SQL queries. It will take me a while to make it a working
> relational database.
>
> Rich
>
>
>