Problem with Ctrl+F

drecksgekritzel
Member Posts: 37
Hello,
we have a problem with the search window (CTRL+F).
if we open the window and search with the option "from the beginning of the field" or "only the complete field" the search works fine and we get a lot of results.
But if we search with the option "part of the field" or with placeholders like *med* we don't get any results.
we think it has to be a configuration problem in the sql server because we did a backup of the sql database from our customer and installed it on our sql server. Now it works...
So can you please give me instructions what we have to change at the sql server from our customer that it works there, too?
P.s. the version number is 3.60 and a SQL database.
Thanks
Kind Regards
Alex
we have a problem with the search window (CTRL+F).
if we open the window and search with the option "from the beginning of the field" or "only the complete field" the search works fine and we get a lot of results.
But if we search with the option "part of the field" or with placeholders like *med* we don't get any results.
we think it has to be a configuration problem in the sql server because we did a backup of the sql database from our customer and installed it on our sql server. Now it works...
So can you please give me instructions what we have to change at the sql server from our customer that it works there, too?
P.s. the version number is 3.60 and a SQL database.
Thanks
Kind Regards
Alex
0
Comments
-
1) If you are searching for part of the field, you are not using * as placeholder, else it will search for * as a character. Placeholders are used in filtering, not searching.
2) There can be difference in the MS SQL Database collation between your and customer server.0 -
thanks for your fast reply.
ok. i tried the search for part of the field with placeholders *. for sure it works but your in right because it makes no sense
and it although didn't work...
can you maybe describe more exactly where can be the difference in the sql server?0 -
If you transfered the DB by making NAV backup, you needed to create your own new SQL database before restoring the backup. And when creating the database, you are choosing which Collation (Sorting order and codepage) you want to use for the database. And there can be the difference between your DB and customer's DB. Check, if you are using same collation.
Another possiblitity is to start SQL Profiler and catch the SQL commands which are sent to SQL when you are searching. Than you can compare the output for you DB and customer DB.
Another difference can be in the "Search as you type" option, which can be disabled in one case and enabled in another one.0 -
Unfortunately i can not test this until the 25th February, because i am not in firm for the next two weeks.
but when i got any results i will post them!0 -
hello, now I am back in office and I have tested it via vpn in the other firm. it works!
It seemed to be a local configuration problem...
Thanks for your help anyhow!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions