Problem solved! I'd built the server with the latest R3 version while the test
server was running Hotfix 4. I re-built the server with HF4 and all is right
with the world.
Robert
> On Dec 6, 2018, at 7:33 PM, Robert ListMail via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Error: “The
I know I’ve swapped .4DC files for minor structure updates in the past on
built-servers; yet, I just swapped out the entire “Server Database” folder in
the built client and I’m now setting an error that I’ve never seen before. I’m
sure I could copy over the massive server build and be done with
Robert, don’t know it this is relevant to your situation but many years ago, to
get around the problem of losing the backup settings when installing a new
built application version, I setup a system where, on quit, I stored the
backups xml file in the data folder (or a record in the data - too
I only rebuild the entire client and server if there has been a 4D version
change ie moving from 16.3 to 16.4 etc. Otherwise I build the server and
just copy across the new .DC file from the Server Database folder. You
need to make sure compiling on same version as deploying. Never had a
problem
to restore local backup settings
(because the backup settings file is always located inside the application's
preferences folder)
I wrote this
https://github.com/miyako/4d-utility-backup-dialog
to get/set all settings as a single object (object notation required).
I have a similar solution
Thanked Kirk, Tim & Tim! :) This is what I thought you guys might say….
So, do you use the XML to do the build or the standard GUI?
R
> On Oct 16, 2018, at 2:39 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>
> The “Best Practice” is to do what 4D TS says
On Oct 16, 2018, at 2:00 PM, Robert wrote:
> I recently started to use built client/server more often since I inherited a
> client that was already doing that. I was told by another developer that when
> doing a structure change that I can simply swap the .4DC file and I’m done.
> 4D TS
Robert,
I wouldn't presume to argue with Tim on best practices but will say I've
been doing those sorts of updates to my built server app for - years. I've
never has an issue that tracked back to it. Yet.
The main benefit is users don't have to wait through downloading a new set
of
Just to clarify -
The suggestion from 4D Technical Support is to include 100% of the entire
application package that is built by 4D. Typically this is done by archiving
the application in a ZIP file or on a DMG and transferring the archive to the
destination machine where it is unarchived. You
I recently started to use built client/server more often since I inherited a
client that was already doing that. I was told by another developer that when
doing a structure change that I can simply swap the .4DC file and I’m done. 4D
TS suggests that this is not wise and that I should probably
10 matches
Mail list logo
