runtime error 75
runtime error 75
runtime error 75
runtime error 75
runtime error 75
runtime error 75 runtime error 75 runtime error 75 runtime error 75 runtime error 75 runtime error 75 runtime error 75 runtime error 75
runtime error 75 runtime error 75
runtime error 75
Go Back  Xtreme Visual Basic Talk > > > runtime error 75


Reply
 
Thread Tools Display Modes
  #1  
Old 11-21-2017, 10:57 AM
starmanMike starmanMike is offline
Junior Contributor
 
Join Date: Oct 2005
Location: near Norwich, UK
Posts: 294
Default runtime error 75


Hi, this is quite perplexing!
I am currently running an app (used the P&DW) and have been for some time quite successfully, but recently noticed a bug. Basically there is a dropdown box to enter one-letter 'error codes' for astronomical observations, which get written to a text file which is then subnitted to HQ. All works swimmingly apart from the fact that if I have used an error code (these are quite rare) on a given observation, then the next observation retains this code in the text file report - so I need to reset the dropdown box's listIndex to -1.

Okay, done that and recompiled the file as an .exe, copied it over to the laptop (where the app resides) but now when I try and run the app, I get a 'file unavailable' message box featuring run-time error '75'. This has not happened on previous occasions when I updated the .exe file.
So I used the P&DW on the main machine to make a new setup package, moved the laptop app over to a memory stick, and installed the whole app again onto the laptop.
Same result! Runtime error '75' again, even with a 'new' app. So I have had to reinstall the previous version, which works fine (apart from the bug). It doesn't say 'whose' runtime error it is - whether visual basic, windows generally, access (the app uses an .mdb database) or whatever.
Sorry for the long explanation, but I feel that the background info might help.
Reply With Quote
  #2  
Old 11-27-2017, 04:23 AM
Daigon Ali Daigon Ali is offline
Regular
 
Join Date: Aug 2014
Location: London
Posts: 64
Default

Have you identified the line of code which raises this error?
Reply With Quote
  #3  
Old 11-27-2017, 05:58 AM
dilettante's Avatar
dilettanteruntime error 75 dilettante is offline
Underclocked lifestyle

Forum Leader
* Guru *
 
Join Date: Feb 2005
Location: Michigan, USA
Posts: 4,529
Default

Sure sounds like it may be tripping over a protected filesystem location.

Don't put writeable files into Program Files.

If you put them into an app-specific subfolder you create under [CommonAppData] (a.k.a. ProgramData) note that be default such folders and files have "CREATOR OWNER" security. The original creator "owns" the item, others can read it but cannot write or delete such items. Your installer should ideally create the folder and set desired access on it instead (for example "Full Control" for "Everyone"). If your installer can't do it your program can check for the folder and if not there create it and set the security on it (elevated rights not required). use a unique subfolder name to avoid colliding with other applications, usually something like [compayname]\[appname].
Reply With Quote
  #4  
Old 11-27-2017, 11:23 AM
starmanMike starmanMike is offline
Junior Contributor
 
Join Date: Oct 2005
Location: near Norwich, UK
Posts: 294
Default

Okay and thanks - problem over (though not solved) as I realised since this is for my personal use only I could simply run the .exe file 'as is' without any need to install as a standalone application, and can even set the app's exe to run on startup.
Reply With Quote
  #5  
Old 11-28-2017, 10:52 AM
starmanMike starmanMike is offline
Junior Contributor
 
Join Date: Oct 2005
Location: near Norwich, UK
Posts: 294
Default

Hi, just a bit of background info - the installer doesn't create the folder, but on first-time startup the app runs a check to see if a couple of folders exist in app.path, and creates them if they don't. The folders are called (app.path)+ "/charts" and "/obs". I've checked, and these folders are created under app.path. So it does just what you recommend but I don't know how to set any sort of security through coding (didn't even know it was necessary!) Thanks for your help, and information.
Reply With Quote
  #6  
Old 11-28-2017, 01:15 PM
Cerian Knight's Avatar
Cerian Knightruntime error 75 Cerian Knight is offline
Polymath (in disciplina)

Super Moderator
* Expert *
 
Join Date: May 2004
Location: Michigan
Posts: 4,199
Default

What is the full path for App.Path?
__________________
I got all the answers wrong on the GLAT, apparently even #9 (where I put a period in the middle of the box and labeled it 'singularity ripe for rapid inflation').
Reply With Quote
  #7  
Old 11-28-2017, 04:03 PM
dilettante's Avatar
dilettanteruntime error 75 dilettante is offline
Underclocked lifestyle

Forum Leader
* Guru *
 
Join Date: Feb 2005
Location: Michigan, USA
Posts: 4,529
Default

Quote:
Originally Posted by starmanMike View Post
So it does just what you recommend but I don't know how to set any sort of security through coding (didn't even know it was necessary!) Thanks for your help, and information.
No it doesn't do what I recommended, it does the opposite. Don't put writable folders and files under Program Files, which is where App.Path would normally point to in an installed application.

Instead use the ProgramData folder, and use a stronger name for your app folder under that to avoid potential collisions with other applications. These folders have CREATOR OWNER access by default, so to make them writable for Everyone you'd have to create the desired access on them after you create them.

The only alternatives I know of include the "Public" special folder (Vista and later) or another drive (e.g. D:) that has no access control on it.


Only use App.Path for (1.) read-only files, and (2.) throw-away programs that will never be installed.

These have been the rules ever since NT came out. Some people limped along on NT 4.0, Windows 2000, and Windows XP by making all users members of either Administrators or Power Users. Those days are long gone. Welcome to 2006!
Reply With Quote
Reply

Tags
app, error, file, runtime, laptop, text, previous, .exe, observation, code, bug, p&dw, box, dropdown, setup, explanation, package, moved, installed, stick, memory, feel, happened, occasions, updated


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Forum Jump

Advertisement:





Free Publications
The ASP.NET 2.0 Anthology
101 Essential Tips, Tricks & Hacks - Free 156 Page Preview. Learn the most practical features and best approaches for ASP.NET.
subscribe
Programmers Heaven C# School Book -Free 338 Page eBook
The Programmers Heaven C# School book covers the .NET framework and the C# language.
subscribe
Build Your Own ASP.NET 3.5 Web Site Using C# & VB, 3rd Edition - Free 219 Page Preview!
This comprehensive step-by-step guide will help get your database-driven ASP.NET web site up and running in no time..
subscribe
runtime error 75
runtime error 75
runtime error 75 runtime error 75
runtime error 75
runtime error 75
runtime error 75 runtime error 75 runtime error 75 runtime error 75 runtime error 75 runtime error 75 runtime error 75
runtime error 75
runtime error 75
 
runtime error 75
runtime error 75
 
-->