NetTalk Central

Author Topic: Possible bug with deleting records from browse  (Read 3785 times)

Mike Grigsby

  • Sr. Member
  • ****
  • Posts: 380
    • Yahoo Instant Messenger - onthedotsoftware
    • View Profile
    • MyHomeAssets! Software (among others)
Possible bug with deleting records from browse
« on: August 25, 2009, 12:14:55 PM »
I've got a very simple supporting record of SysID, Make, and an image, which I'm not really using.

The file has about 60 records in it, and the browse has about 12 lines per page.

I hit the button to jump to the last page and delete the record at the top. It goes to a white page that says "Page not found" and the URL is "http://74.60.133.68:4606/-1?FromForm=MakeF".

If I use the Back button on the browser, and press Resend on the popup, it goes back to the list, and the record is deleted.

I'm on the latest build that was on the site on Friday: 4.36?

I can duplicate it each time and it does it for every kind of record when doing this keystroke combination. Any ideas?
Mike Grigsby
Credify Systems
Central Oregon, USA

Rene Simons

  • Hero Member
  • *****
  • Posts: 650
    • View Profile
Re: Possible bug with deleting records from browse
« Reply #1 on: August 25, 2009, 01:00:05 PM »
Mike,
Did you copy the Web Folder as well from libsrc to your app directory?
Rene
Rene Simons
NT14.14

Mike Grigsby

  • Sr. Member
  • ****
  • Posts: 380
    • Yahoo Instant Messenger - onthedotsoftware
    • View Profile
    • MyHomeAssets! Software (among others)
Re: Possible bug with deleting records from browse
« Reply #2 on: August 25, 2009, 04:52:43 PM »
I'm pretty sure I did, but I'll try it again to be sure. I wish there was an easier way to copy new code to an existing program. It's a royal pain when you've heavily modified styles and what not.
Mike Grigsby
Credify Systems
Central Oregon, USA

vsorensen

  • Jr. Member
  • **
  • Posts: 52
    • View Profile
    • Email
Re: Possible bug with deleting records from browse
« Reply #3 on: August 25, 2009, 06:03:30 PM »
Have you tried the 4.37 pre-release posted yesterday?  It solved a number of problems I was having that were introduced in 4.36.