Veda2.0 Released!


importing results
#1

When starting to import results into VEDA-BE, after choosing the desired scenario to import, an error message turns up in my screen.

It's the first time I run TIMES and my scenario is TIMES_DEMO.
The error report is:
               DAO.tableDefs
               3441
              The field delimiter of the text file matchs with the decimal delimiter or the text delimiter.
If someone has have the same problem or know how to solve it...
Thanks!!!
         
Reply
#2
The easiest way to fix this is to use "English US" (or UK) as the language that decides number formats. This is available under Control Panel - Regional Options. Let me know your OS if you can't find this option quickly.
A more elegant solution will be available soon.
Reply
#3
working!!
thanks!!
Reply
#4

Amit:

When I import results (of an existing case/scenario) into VBE, I am getting the following error message. 

“Microsoft JET Database Engine

-2147217843

Not a valid password”

Any idea, what’s wrong?  I thought that the same scenario data has been displayed in a open table, but it was not a case.  I closed all tables before reimporting the results.

It doesn’t seem to be harm but sometime it’s annoying.

Thanks

Kannan

The log file excerpt

Version: 4.8.7
02.03.2011 16:49:50
Error in procedure codeSmart//
Source = Microsoft JET Database Engine
Number = -2147217843
Description = Not a valid password.
Error Stack  : cmdOK_Click() : PerformTasks() -> Stage 4
Veda_BE.modVeda.GenerateDimTables [650]
Table View:- [cost1]
 Attribute = VAR_Act
 Attribute = VAR_Cap
 DataValues = PV
 Period = 2048
 Period = 2100
 ProcessSet = HYD-DAM
 ProcessSet = HYD-RUN
 Scenario = HyP-A
 Scenario = Ref-A
 

Reply
#5
Veda_BE487413.zip try this beta EXE
Reply
#6
(03-03-2011, 03:21 AM)AKanudia Wrote: Veda_BE487413.zip try this beta EXE

I am having this issue as well. I'm only experiencing it at the end of batch runs and only the last case that's running. Would you be able to send me a copy of the .zip you listed above, or is there a more up-to-date fix?

Thanks!
Morgan
Reply
#7
Kindly update Veda applications using the latest VedaInstaller.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Results of UC_Growth are not matching with given constarint Anjali 12 11,186 02-09-2022, 02:03 PM
Last Post: anshfr
  Non-optimal results when 'fixed result to x period' lppnog 1 2,729 30-11-2020, 09:26 PM
Last Post: Antti-L
  CREATING AND IMPORTING NEW SCENARIOS xavier 6 9,697 10-03-2020, 04:59 PM
Last Post: xavier
  TIMES new scenario importing method alexazeze 2 4,793 17-02-2020, 01:00 PM
Last Post: alexazeze
  Results DB Maker and .VD file JasonMcGuire 7 13,513 09-07-2019, 08:31 PM
Last Post: Antti-L
  Results in VEDA BE MohammedAbiAfthab 0 2,272 02-07-2019, 05:39 PM
Last Post: MohammedAbiAfthab
  Could not open results in VEDA-BE Aymane 3 7,410 31-01-2019, 09:08 PM
Last Post: Aymane
  Problem in importing ~COMAGG table saleh 5 12,639 05-12-2017, 11:08 AM
Last Post: Vikrant
  Problem in importing process sets saleh 6 10,638 21-11-2017, 12:59 PM
Last Post: Vikrant
  Errors during importing in VEDA-FE kramea 2 21,839 20-09-2013, 09:40 PM
Last Post: kramea

Forum Jump:


Users browsing this thread: 2 Guest(s)