Hi.
I've had a frustrating night... I hope someone can help!
Here's the story. I just uploaded my application to a new server with SQL Server 2016 installed on both systems (NOT SQL Server Express). The components and pages uploaded perfectly, as did the databases (some of the older components are using MS Access Tables that I inherited... more on that later).
The application lets me login, without problems (using DBF web security), AND lets me work with any component/page that uses the MS Access tables (explained above). BUT, EVERY UX or Grid that uses the SQL Server Tables gives this error:
The application works fine on the "localhost". I can log onto the Server and log in to SQL Server (Management Studio) and open and read the tables... no issues. I did NOT alter the "default packet size" on either system (both set to the default 4096). I even tried creating a new "connection string" to a new table that was created on the server (and backed up and restored onto the local machine). Again, it works fine on the localhost, but the server gives the same error as above.
Everything worked fine on the previous server.
I'm completely lost. Hopefully, someone out there has seen this before and will have a suggestion. I'd appreciate any help or suggestions.
Thanks
I've had a frustrating night... I hope someone can help!
Here's the story. I just uploaded my application to a new server with SQL Server 2016 installed on both systems (NOT SQL Server Express). The components and pages uploaded perfectly, as did the databases (some of the older components are using MS Access Tables that I inherited... more on that later).
The application lets me login, without problems (using DBF web security), AND lets me work with any component/page that uses the MS Access tables (explained above). BUT, EVERY UX or Grid that uses the SQL Server Tables gives this error:
The application works fine on the "localhost". I can log onto the Server and log in to SQL Server (Management Studio) and open and read the tables... no issues. I did NOT alter the "default packet size" on either system (both set to the default 4096). I even tried creating a new "connection string" to a new table that was created on the server (and backed up and restored onto the local machine). Again, it works fine on the localhost, but the server gives the same error as above.
Everything worked fine on the previous server.
I'm completely lost. Hopefully, someone out there has seen this before and will have a suggestion. I'd appreciate any help or suggestions.
Thanks
Comment