Re: "Microsoft Access" for RDF?

No, this is dangerous and is hiding the truth. Take the red pill and admit
to the user that this particular property is unordered, for instance by
always listing the values sorted (consistency is still king).

Then make it easy to do lists and collections.

Don't let the user encode information he considers important in a way that
is not preserved semantically.

If you are limited by typing of rdf:List elements, then look at  owl
approaches for collections that allow you to order items and use owl
reasoning for list membership - see
https://code.google.com/p/collections-ontology/

Ordering of which properties to show in which order on a form is another
matter, that is a presentational view over the model. The :View could
simply be a choice of an owl:Class and a partial order of owl:Properties
instances of that class "should have".