Recent

Author Topic: Alternative to shortcut  (Read 265 times)

lawman

  • New Member
  • *
  • Posts: 40
Alternative to shortcut
« on: January 27, 2020, 03:38:22 pm »
I want to keep a windows app and sqlite db on a mapped network drive, to be accessed by multiple users.

I'm hoping this removes the need to keep the app on each user's local pc, as updating becomes an issue.

Tried creating a shortcut link, but running that always gives security warning that network app creator is unknown.   Can still press continue and run file.

Instead of a shortlink, I'd like to create a small pascal exe which simply runs the network stored exe app, then shut itself down.

Whats the best way to do this?

thanks

marcov

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 7928
Re: Alternative to shortcut
« Reply #1 on: January 27, 2020, 04:12:42 pm »
Migrate to a client server solution as quick as possible and dump sqlite?

Running multiuser file based databases in combination with networking requires all kinds of locking issues.

ASBzone

  • Sr. Member
  • ****
  • Posts: 298
  • Automation leads to relaxation...
    • BrainWaveCC Utilities
Re: Alternative to shortcut
« Reply #2 on: January 27, 2020, 05:26:06 pm »
Migrate to a client server solution as quick as possible and dump sqlite?

Running multiuser file based databases in combination with networking requires all kinds of locking issues.
;D
-ASB: https://www.BrainWaveCC.com

Lazarus v2.0.7 r62618 / FPC v3.2.0-beta-r44160 (via FpcUpDeluxe) -- Windows 64-bit install w/32-bit cross-compile
Primary System: Windows 10 Pro x64, Version 1909 (Build 18363.657)
Other Systems: Windows 10 Pro x64, Version 1909 or greater

lawman

  • New Member
  • *
  • Posts: 40
Re: Alternative to shortcut
« Reply #3 on: January 27, 2020, 06:30:15 pm »
Lol

dB concurrency aside, what's best way for app 1 to run app 2.

Then either close or continue depending on separate issues

Thx

garlar27

  • Hero Member
  • *****
  • Posts: 633
Re: Alternative to shortcut
« Reply #4 on: January 27, 2020, 07:22:34 pm »
Lol

dB concurrency aside, what's best way for app 1 to run app 2.

Then either close or continue depending on separate issues

Thx

What marcov said is the best way to go.

If not the only thing I can think of is is a Client and a Server app where the server handles the writings so they don´t overlap SQLite is not prepared for simultaneous writing.