Re: Upsizing To SQL Server

Well, this is fascinating; it's been an eye opener for me. I had the
gut feeling that many people look at Access with disdain because you
don't need to overcomplicate your life with specialising on complex
architectures involving different skill sets (presentation layer,
reporting layer, business logic layer, database layer and so on) - you
can do it all with one application!

I have many stories on how people change their mind about Access after
they've seen what it does. Systems that were quoted for ~$150,000 (and
4 months delivery) with a complex architecture could be built in
Access part-time in 2 weeks as a working proof of concept and then
they could be tailored and strengthen to suit the business needs in
again 2 weeks part-time work.

But I have 3 situations were I am hitting some limits with Access
(well, perhaps the limit is me!) and would like to know how to go
about it (and don't know whether SQL server is the right answer):

1) Authentication / Authorisation using Active Directory (LDAP): I am
not after a purist solution here; I'd be over the moon if I could
simply authenticate via a login form and if successful then I'd manage
local authorisation in Access

2) WAN deployments: I've tried to use Access Pages but both their look
and functionality seems rather cumbersome to me. Is there any sound
advice regarding deployment on a server and then provide clients with
Remote Desktop, VNC or something else?

3) Cross platform on Client side: Even if Access Pages did work, they
are Windows > Internet Explorer sensitive. Is there a way to allow
Linux / Mac clients to use Access applications that live on a Windows
server?

Any experience / opinion would be greatly appreciated.

.

Relevant Pages

  • Re: Users Cant Access Documents on Server
    ... my computer to the network on the server. ... Connection Wizard none of the computers were listed. ... The Mac clients can not communicate with the server box. ... > Error Messages When You Open or Copy Network Files on Windows XP SP1 ...
    (microsoft.public.windows.server.sbs)
  • RE: Connection problem with 98 station on 2003 AD domain
    ... Thanks for your response and give me a right direction. ... I think the root cause is that those 98 clients do not have SMB ... packet signing enabled and cannot authenticate to a Windows Server 2003 ... How to enable Windows 98/ME/NT clients to logon to Windows 2003 based ...
    (microsoft.public.windows.server.migration)
  • Re: Cannot join Windows 2003 Server to SBS 2000 Domain
    ... this on all client computers at this remote office. ... All the clients but one at the main office are Windows XP Pro. ... > 'adprep' commands on the SBS 2000 server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Users Cant Access Documents on Server
    ... > then add my computer to the network on the server. ... Did you not see the computers in the Server Management taskpad section? ... The Mac clients can not communicate with the server box. ... >> Error Messages When You Open or Copy Network Files on Windows XP SP1 ...
    (microsoft.public.windows.server.sbs)
  • Re: Group Policy Results Wizard
    ... I guess we can rule out Windows ... If you can't reach the WMI from the server you will want to try to reach it ... switching off the Windows Firewall on one of the clients, ... Business Server Windows Firewall" (not Small Business Server ...
    (microsoft.public.windows.server.sbs)
Loading