MS ACCESS 2013

"and forms"
Actually, you cannot change anything in Form design since you cannot open a Form (or Report) in design view in an ACCDE.

The .accde prevents design view access to Forms/Reports/Modules but allows design changes to Tables/Queries/Macros.

So what can be done to prevent access to tables design view and query design view?

If you are only concerned about 'design' view of these objects, either create a  Run Time version or open in the simulated Run Time version - as noted above.

If you are trying to protect data ... then for all practical purposes, after all has been said and done ... at the end of the day ...
Nothing -  wherein you can guarantee 100% that no one can get to the data. You would need to move to SQL server for this.

So what can be done to prevent access to tables design view and query design view?

I told you earlier - rename the file to yourdatabase.accdr.  The .accdr extension tells Access to pretend to be the runtime engine and the runtime engine won't open anything in design view.  But, as I said, this is no protection against mischief but it will keep out ordinary users.

Yes, use one of the three methods allready mentioned for launching the application in runtime.
Also, if possible, write-protect the file. Only few users know how to select Properties of a file and change write-protection. Further, if in a controlled environment - if your users log on in an Active Directory - you can force users to only be granted rights to open and read the file, not alter it. This, of course, requires that you may have to modify your application to not make design changes on its own objects.

/gustav

Is it possible if I can split the database put the forms on the server and put the actual tables and queries on my computer?

Not without significant changes to the app.

If you are really worried about people changing the querydefs, you can embed them as strings in the form/report RecordSources and RowSources.  This is not without problems though.  There is a bug that I ran into again today that causes the SQL string to become the name of a query and so you loose the query string.  The ones you call from code can be turned into strings in VBA.  

The tables will need to move to SQL Server or some other RDBMS that can be secured.

good